>I find that all the issues of the new instance which connect to the slave DB canont be viewed
JIRA requires full read/write access to its database, and it requires a full re-index after any change made to the database that does not go through its API. You can't have a slave database in write mode, and re-indexing your slave JIRA every time the master changes is a non-starter.
In short, what you're trying to do here simply will not work.
By all means, have a slave database replicated from your production, use it for DR (warm standyby), backup, reporting etc. But you can't run a second JIRA against it.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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