Too many events since previous incremental sync
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
Incremental sync mail fail with the following errors in logs:
1
Incremental synchronisation failed: Too many events since previous incremental syncDiagnosis
Environment
Crowd 2.12+ integrated with LDAP
There may other application connecting to Crowd and also receive the same error message
Cause
Incremental syncs rely on checking new changes since the last successful sync. If there are too many change events that have occurred, incremental sync will fail.
The default event limit is 10000
Solution
Workaround
To workaround this problem, wait until Crowd performs a Full Synchronization job. This will ensure that all changes are up to date.
Note you can also force a full sync by modifying Crowd's directory and disabling the "Incremental Sync" function. Then re-enable this after the full sync is complete.
Resolution
It may be possible to increase the event limit by modifying the Java startup parameters for Crowd:
Add the following parameter
1-Dcrowd.eventstore.eventlimit=10000
Increase this value as needed
Restart Crowd
Was this helpful?