Setting a Jira Datacenter in Cluster Mode.

Question

Hi,

We are Setting a Jira Datacenter software(version - 8.8.1) in Cluster Mode. However, when we put this inside AWS Load Balancer, with servers are added in TG(instance_id or IP) it is getting redirected to the login page frequently.

Cluster.properties file:

jira.node.id = *****
jira.shared.home = ******
ehcache.listener.hostName = *****

Please help to debug the same.

Daniel Ebers · Answer

Great! Glad you fixed it!
Thanks for letting us know what the root cause was.

Virender Dubey · Answer

Thanks @Italo Qualisoni [e-Core]  and @Daniel Ebers

I was setting the sticky session config incorrectly and due to this, jira is failing to manage the session.
In AWS sticky session config is present at Target Group Level and we have to set that only. Post setting this it started working.

Italo Qualisoni [e-Core] · Answer

Hi, First I would say that you should look for @Daniel Ebers comment, he mention an article that can help you. You can see what node you are accessing in the bottom of the page, if you refresh the page your node identifier should be the same , if that changes then you should review your sticky session settings. * Scroll down to the bottom of the dashboard page * Check the footer and locate the text Atlassian JIRA Project Management Sofware (v7.X.X#XXXXX-XXXX:XXXXXXX:YOUR-NODE) * Cross reference the footer with your cluster.properties file located in your local home * YOUR-NODE corresponds with the jira.node.id defined in the file * https://confluence.atlassian.com/jirakb/how-to-determine-which-node-a-user-is-accessing-in-datacenter-885252555.html Also I've seen sometime an issue to login due a missing attributes in your connector in $JIRA_BINARY/conf/server.xml I would recommend you to review your server.xml file, since now you are using a LB reverse proxy and you should provide the ProxyName, ProxyPort and Scheme attributes. scheme should be '' proxyName should be '' proxyPort should be '' For insecure you should include these attributes in your Connector and restart JIRA proxyName="jira.yourcompany.com" proxyPort="80" scheme="http" For secure proxy you should include these attributes in your Connector and restart JIRA proxyName="jira.yourcompany.com" proxyPort="443" scheme="https" secure="true" * https://confluence.atlassian.com/jirakb/configure-jira-server-to-run-behind-a-nginx-reverse-proxy-426115340.html * https://confluence.atlassian.com/jirakb/jira-displays-an-error-banner-about-the-incorrect-tomcat-config-939940652.html