-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.13.0, 8.5.3, 8.5.4
-
7.13
-
8
-
Severity 3 - Minor
-
2
-
Issue Summary
It appears that when one node is doing directory sync when it is completed, the timing ("Last synchronization at" )would only be updated on the node that is doing it. The other node would still use the time when is the last time they are doing the sync
Steps to Reproduce
- Set up a Cluster with at least 2 nodes.
- Set up the cluster with External Directory.
- Manually sync the directory in one node (Node A).
- After a few minutes, sync it again in the other node (Node B).
- Check back the timing in the other node (Node A) after the last directory sync
Expected Results
The Node will be updated with the latest directory sync timing that the cluster has done
Actual Results
The Node will still retain the timing when the first time the sync happens.
Workaround
Go to the Scheduler details administration page and search for the com.atlassian.jira.crowd.embedded.JiraDirectoryPollerManager job.
Expanding the details of this job will show the actual time it was performed on any node of the cluster.
- is related to
-
CONFSERVER-52466 Directory Synchronization Time not reflected correctly on both nodes in Confluence Data Center
- Closed
-
JRASERVER-62311 Incremental User Synchronization broken on data center
- Closed
- mentioned in
-
Page Loading...