-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
7.9.0, 7.2.15, 7.6.7
-
7.02
-
7
-
Severity 3 - Minor
-
1
-
Problem.
From Administration > System Info > Cluster Nodes we can see offline nodes listed as ACTIVE when node is shutdown ungracefully.
Steps to reproduce
- install JDC with two nodes (node1, node2)
- force kill (kill -9) node1
Expected outcome
- node1 should listed as OFFLINE in UI and database
Actual outcome
- killed node still listed as ACTIVE
- in the database, we see
jira763=# select * from clusternode; node_id | node_state | timestamp | ip | cache_listener_port | node_build_number | node_version ----------------+------------+---------------+-----------+---------------------+-------------------+-------------- node1 | ACTIVE | 1523489152849 | atlassian.com | 40001 | 76005 | 7.6.3 node2 | ACTIVE | 1523562548096 | atlassian.com | 40001 | 76005 | 7.6.3 (4 rows)
Note this is just UI problem, but the shutdown node is no longer actively communicating with the cluster.
- duplicates
-
JRASERVER-42916 Stale node ids should automatically be removed in Jira Data Center
- Closed
- is related to
-
JRASERVER-59503 /status should return running and not starting when JDC node is already started up
- Closed
-
JRASERVER-67138 /status url returns ERROR instead of MAINTENANCE during foreground reindexing
- Closed
-
JRASERVER-62927 If JIRA has errors during startup, ApplicationStatusServlet doesn't show JIRA state properly and remains stuck in {"state":"STARTING"}
- Gathering Impact
-
JRASERVER-65708 /status returns Maintenance instead of Running when nodes are not in Maintenance mode and the Database is configured with an unsupported collation
- Long Term Backlog
- mentioned in
-
Page Loading...