-
Bug
-
Resolution: Fixed
-
Medium
-
5.9.1, 5.8.17
-
4
-
Severity 2 - Major
-
Basically, after Crowd upgrade or recreation of Crowd directory, Confluence will trigger full synchronisation which will repopulate the number of user from Crowd directory. This involved adding and updating user as per stack trace below:
2016-09-19 21:15:31,022 INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] getUsersToAddAndUpdate scanning [ 90786 ] users to add or update
This operation slows down significatly due to a large user base (90140 users and 269190 of group membership)
2016-09-19 21:16:39,947 INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (841/90140 - 00.9%) 60032ms elapsed 2016-09-19 21:17:40,046 INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (1287/90140 - 01.4%) 120133ms elapsed 2016-09-19 21:18:40,288 INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (1627/90140 - 01.8%) 180375ms elapsed
After 3 days:
2016-09-22 14:06:29,803 INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (52575/90140 - 58.3%) 233449890ms elapsed
Completed after 10 days:
INFO [scheduler_Worker-2] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (90135/90140 - 100.0%) 743764777ms elapsed
This issue does not trigger under normal circumstances (Confluence restart/reenabling Crowd directory in Confluence)
- blocks
-
CWD-4344 Significantly Slower Sync to Confluence or JIRA in Crowd 2.8 due to /rest/usermanagement/1/group/membership
- Closed
- incorporates
-
CONFSERVER-43156 Sessions are never cleared during LDAP user directory sync
- Closed
-
CONFSERVER-45698 Confluence 5.9+ much slower to sync users and remove users from groups compared to 5.8
- Closed