>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.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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