-
Suggestion
-
Resolution: Unresolved
-
None
-
7
-
6
-
Problem Definition
In some situations JIRA DC have stale/lost cluster lock. Normally you can check this by navigating to Cluster Locks check [ System > Support Tools > Instance health > Cluster Locks ]. Problem that JIRA Admin space (mentioned check is under that space) uses lock com.atlassian.jira.config.DefaultReindexMessageManager.messageLock, so if it's lost, than it's impossible to check the locks.
Suggested Solution
Create separate Cluster Status space which:
- will not use any lock to access it
- will show all current Cluster locks with following data:
- Lock name - Node - Age
- (Advanced) will be able to break/steal Cluster lock
Workaround
Check DB table clusterlockstatus:
select * from clusterlockstatus where locked_by_node is not NULL;
- relates to
-
JRASERVER-66597 JIRA DC might lose Cluster lock due database connectivity problems
- Closed
-
JRASERVER-66658 JIRA does not retry cluster unlock actions after database connectivity problems
- Closed
-
JRASERVER-65890 Create logging event for clusterlockstatus during startup
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...