You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey guys,
I think I need a better explanation about how the secondary.shared-home works
- I put in jira-config.properties a value: disaster.recovery=true
- I put in cluster.properties where the primary shared-home is mounted (pointed to the NFS)
- I put in cluster.properties the secondary shared-home location what's basically mounted over NFS
and now:
- the primary shared-home is used properly
- the secondary shared home is synced to the primary so it's the same. It's syncing all of the time.
- as I understood the secondary shared home is located in the /jira-shared-home/secondary
- as I understood, the secondary shared home may be pointed directly to the VM B which is syncing constantly to the VM A. If that's correct?
- I cannot find a proper info if that's fine to put disaster.recovery=true along over nodes (?)
- In this scenario basically the DRC mechanism could be set in a bit different manner:
a) node A + B sharing the same (replicated) DB
b) node A uses shared-home A
c) node B uses shared-home B
d) shared-homes are fully synced to each other
with no need to put disaster.recovery=true value.
And all I would need is to cover the availability checks regarding to each node on LB?