Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restart JIRA on AKS #99

Open
swathiAMD opened this issue Aug 20, 2019 · 1 comment
Open

Restart JIRA on AKS #99

swathiAMD opened this issue Aug 20, 2019 · 1 comment

Comments

@swathiAMD
Copy link

Hi,

I have installed this JIRA image on the AKS cluster and the JIRA pod connected to an external mysql database. Due to some issue the pod got destroyed and new pod got created which shows me the setup page. I have set up the JIRA on new DB. I have changed the dbconfig file to point to old DB which has all the data. I have to start and stop the JIRA for the DB connection to re-established. When i stop the JIRA pod , the pod is getting destroyed and new pod is getting created. I m not sure how to find the pods are getting destroyed.

Can anyone please help me .

Thanks,
Swathi S

@TheKas
Copy link

TheKas commented Sep 4, 2019

When setting up Jira or Confluence behind a (GCE/AWS/other) proxy/load balancer, make sure to setup proxy/load-balancer timeouts to large values such as 300 secs or more. (The default is set to 60 secs). It is very important to setup these timeouts, as Jira (and other atlassian software) can take significant time setting up initial database. Smaller timeouts will panic Jira and Confluence setup process and it will terminate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants