LDAP Synchronization Running Very Very Slowly

The initial configuration and import of the LDAP into confluence ran really fast (~2 hours). We had to update the field mapping to remove the displayName (our ldap displayName field does not contain a readable name). To do this we entered a field name that does not exist in the LDAP (ex: "User Display Name Attribute:*" = "dummyValueThatDoesNotMatchLDAP"). After making this change the LDAP starting a full sync and ran well for a number of hours. However it has been slowing down ever since. Currently we are processing roughly 4 users a minute. At this rate it will be another 4 days until the sync finished (We started this 4 days ago). Also the processing rate is slowing so I'm concerned it will not finish. Our CPU usage is now almost maxed out. 

I'm seeing this in the log files:

2016-03-07 16:19:46,738 INFO [scheduler_Worker-1] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (65097/104641 - 62.2%) 338414832ms elapsed
2016-03-07 16:20:21,482 WARN [scheduler_Worker-1] [confluence.util.profiling.DurationThresholdWarningTimingHelperFactory] logMessage Execution time for publishing event com.atlassian.crowd.event.user.UserEditedEvent@c213059 took 9137 ms (warning threshold is 5000 ms)
2016-03-07 16:20:38,389 WARN [scheduler_Worker-1] [confluence.util.profiling.DurationThresholdWarningTimingHelperFactory] logMessage Execution time for publishing event com.atlassian.crowd.event.user.UserEditedEvent@c213059 took 6994 ms (warning threshold is 5000 ms)
2016-03-07 16:20:58,914 WARN [scheduler_Worker-1] [confluence.util.profiling.DurationThresholdWarningTimingHelperFactory] logMessage Execution time for publishing event com.atlassian.crowd.event.user.UserEditedEvent@c213059 took 8889 ms (warning threshold is 5000 ms)
2016-03-07 16:20:58,915 INFO [scheduler_Worker-1] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] logIfNecessary updating users - (65101/104641 - 62.2%) 338487009ms elapsed

1 answer

Hi Stephen, 

Thank you for your quick response! The normal syncing to confluence from our LDAP was working great. However a change in the "User Schema Settings" caused the syncing to run a crazy long time. In our non-production environment we tested this and once the updated schema sync finished the normal syncing worked great. Is there something we can do to get through the update sync?

Thank you,

-Tim Patton

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

463 views 6 6
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you