-
Bug
-
Resolution: Fixed
-
High
-
None
-
8.0.0, 8.5.19, 8.19.1, 8.13.27, 8.20.18
-
8
-
Severity 2 - Major
-
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Create a multinode (8) Jira DC environment
- Connect a remote directory with 100k users
- Start&stop node in cluster
Expected Results
All nodes have a consistent state of the user/group caches.
Actual Results
User may be missing in cache and Jira functionality based on this cache may not be able to find a user....
Workaround
- Full cluster stop
- Start node and check if user/group caches state is as expected
- Only start new nodes if all nodes in current cluster has the correct state of the user/group caches
- relates to
-
JRASERVER-72101 Performance regression in user lookup
- Closed
-
JRASERVER-70690 User login fails because inconsistent data / uk_mem_parent_child_type
- Closed
-
JSWSERVER-20336 Searching and Mentioning users may cause performance issues and high CPU load
- Closed
-
JRASERVER-71483 As a Jira admin I would like to recover from user cache corruption without a whole cluster restart
- Closed
-
LOGIN-60 Loading...
- mentioned in
-
Page Loading...