Here is the scenario. We currently have a high availability infrastructure with our internal JIRA instance. It includes a MySQL master DB and slave DB and one Production JIRA instance. We want to stand up a second internet facing read-only JIRA instance. We want to use the slave DB as master and chain another slave DB from that to which our internet facing JIRA instance will access with a read-only user. I am proposing to have MySQL slave DB (C) with MySQL DB (B) as master which is slave to MySQL DB (A). Production JIRA connects to (A). New read-only internet-facing JIRA would connect to (C). Is this possible or will internet-facing read-only JIRA still need to or attempt to make updates to DB (C)?
JIRA requires full read/write access to its database. It won't even start without it (for safety). So you'd have to have the slave enabled for write access. Then your second JIRA would stomp all sorts of damage over your production data.
It's fine to replicate the data, report off it, read it, use it to create the backups and have it as a warm (but not hot) standby. But you can't run two JIRAs against a single data set.
Right, now I've jumped all over that idea... Have a look at JIRA Data Centre.
Not quite. It's the same data you are hitting, so the permissions and issue security are identical on all nodes. Note that your plan to have internal and external facing systems won't work properly either - JIRA needs to be run on one single url, it can't have two.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs