When a node is suddenly terminated (ie not shutdown gracefully), ClusterManager API still return the terminated node as active
From the app developer
I have 2 node cluster of JIRA 7.9.0 (node1, node2). Each node is a docker. When I turn off node2 by stopping the docker container the other node still sees second node as active.
I've checked that in clusternode table node2 is active. I've checked that in clusternodeheartbeat table beat data are not updated when node2 is down.
The way I am getting node data:
When instead of killing node2 I shut it down gracefully (/etc/init.d/jira stop), then node2 status in clusternode table is updated to OFFLINE.
Jira should make use of clusternodehearbeat table to determine whether node is OFFLINE
Tables data after node2 was terminated - not gracefully
3) I killed a note to simulate a failure in DC cluster. In my case I stopped a docker on which Tomcat with Jira node was placed.
- Have 2 nodes
- Terminate node 2 instead of shutting down gracefully
When node2 is down other nodes should see it as offline.
When node2 is down other nodes see it as online.
- I haven't personally replicated this. I'm moving this in this project for more expertise
Currently there is no known workaround for this behavior. A workaround will be added here when available