Details
-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
6.4.5
-
6.04
-
Description
Summary
User Directory synchronization takes a long time deleting the same users on every synchronization.
Environment:
- LDAP Connector directory;
- JIRA 6.4.5.
Steps to Reproduce
- Add a LDAP Connector directory
- Create user in the LDAP directory and synchronise with JIRA
- Assign an issue to one LDAP user
- Delete the assigned user from LDAP server
- Synchronise the directory
Expected Results
JIRA should run the delete upon the synchronisation adding the deleted_externally flag to the cwd_user table once.
Actual Results
The expected operation will run upon every synchronisation.
The following is shown in the logs on every synch.
2015-03-26 12:01:55,978 atlassian-scheduler-quartz1.clustered_Worker-1 DEBUG ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] user [ user ] not found, deleting 2015-03-26 12:01:55,978 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 10148 ] users for delete in DB cache in [ 7ms ] 2015-03-26 12:01:55,978 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleting [ 1 ] users 2015-03-26 12:01:55,981 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleted [ 1 ] users in [ 3ms ] 2015-03-26 12:01:55,981 atlassian-scheduler-quartz1.clustered_Worker-1 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 10ms ]
Notes
This can make the synchronisation take a long time when a huge amount of users have been deleted from LDAP.
Attachments
Issue Links
- relates to
-
-
- Long Term Backlog
-