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

Multiple replication not working in latest version of JIRA #278

Closed
abhattarai-athene opened this issue Aug 27, 2021 · 5 comments
Closed
Labels
bug Something isn't working

Comments

@abhattarai-athene
Copy link

abhattarai-athene commented Aug 27, 2021

The Cluster Cache Replication health check has failed in your system.

@abhattarai-athene abhattarai-athene added the bug Something isn't working label Aug 27, 2021
@bianchi2
Copy link
Collaborator

@abhattarai-athene could you please provide more info like logs, screenshots or just elaborate on what's happening when you scale Jira stateful set? Depending on what exact error you see, troubleshooting steps will differ.

@abhattarai-athene
Copy link
Author

Hello @bianchi2 ,
Looking at clustering section from admin, I cannot get the details about jira-1. I cannot see much from jira logs about replications. Also running telnet command from inside pods jira-1, it was not able to resolve name jira-0.
image

Below screenshot , you can see application status as running for jira-0 but not for jira-1. It only says jira-1 and jira-0 active.
image

@errcode1202
Copy link
Collaborator

Hi @abhattarai-athene, Jira suffers with issues relating to indexing and clustering regardless of K8s. A number of these issues in particular are encountered more often when running Jira in a K8s cluster. These have recently been documented here. Can you please follow the recommended advice on scaling jira to see if that improves things.

@nanux
Copy link
Member

nanux commented Sep 15, 2021

Hi @abhattarai-athene, can you please confirm if this issue is the same as the one listed by @errcode1202? If it is the same, can you please close this ticket as we track the issue elsewhere and provide workaround?

@abhattarai-athene
Copy link
Author

The issue is resolve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants