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
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.
We are setting High Availability in our JIRA PostgreSQL database for Jira datacenter.
We would like to know how to specify two postgresql datasources (one open in read-write, another one open in read-only).
Particularly is there is a way for JIRA to distinguish read-only and read-write PostgreSQL servors
(In case of database service issue, our PostgreSQL clusters will databases will failover (automatically).
First of all, Happy new year and thank you for the response.
We are trying to point Jira to two databases:
- primary database (read,write) (master)
- standby database (read only) (slave)
The goal is if the master database server down, the slave replaces it.
Please could you tell us what you are trying to achieve here? Please don't repeat the same question again - your question was perfectly clear that you want some form of failover.
Why are you trying to do this? What does the end-user get out of it? Are you looking for high availability, some form of disaster recovery, performance, or something else for example?
Why? What problem would "database high availability" solve?
Do you mean general "high availability" of a Jira system?
Ok, thanks! I know it's been a bit repetetive, but it's important that I don't answer the wrong question.
Database high-availability is a component of high-availability for a system, but you do not do it at the application level. In fact, you can't do it at the application level if you've got a clustered application.
If you want a highly available database to support your HA Jira DC cluster, then you need an HA database service (almost certainly a cluster). Replication and secondary sources are not highly available database solutions, they're backup and failover solutions.