We are using Jira datacenter on AWS with 3 nodes. Out of 3 Jira nodes, 2 are in active state and 1 node is kept passive (for replication). I am unable to find the configuration settings to make the Jira node passive; means jira service is running on all 3 nodes but on 2 nodes i am getting the response of http:8080/status code so they are in service in Load Balancer and on 1 node i am not giving the response of http:8080/status command, so it is Out of Service in the Load Balancer.
#Running Node Status command output
[root@ip-172-*-17-44 ec2-user]# curl -v localhost:8080/status
- Trying 127.0.0.1...
- Connected to localhost (127.0.0.1) port 8080 (#0)
< HTTP/1.1 200
< Cache-Control: private
< Expires: Thu, 01 Jan 1970 00:00:00 UTC
< X-AREQUESTID: 1093x72055518x1
< X-ANODEID: i-00e6cc29364553ffa
< X-ASEN: SEN-10124550
< Set-Cookie:
atlassian.xsrf.token=B5K4-34DH-08CH-P090|34e77460c0c15326f13aa9c38cae4b7ced9286a2|lout;path=/;Secure
< X-AUSERNAME: anonymous
< X-Content-Type-Options: nosniff
< Content-Type: application/json;charset=UTF-8
< Content-Length: 19
< Date: Tue, 03 Sep 2019 18:13:18 GMT
< - Connection #0 to host localhost left intact
#Passive Node Status command output
[root@ip-172-*-17-193 ec2-user]# curl -v localhost:8080/status
- Trying 127.0.0.1...
- TCP_NODELAY set
- Connected to localhost (127.0.0.1) port 8080 (#0)
- Recv failure: Connection reset by peer
- stopped the pause stream!
- Closing connection 0
curl: (56) Recv failure: Connection reset by peer
As passive node is not giving status 200 for lcoalhost:8080/status command , Load Balancer assumes it to be unhealthy and kept it OutofService. I am unable to find the configuration change which needs to be done on passive node to make it behave like this.
