perhaps opposite to one jira - two databases I read, which commented by @Nic Brough [Adaptavist]
my question :
one database serving two jira instances would cause disaster ? dbconfig.xml will be same on the database connection, I think, so wonder is it possible I run jira 1 on one machine to access database 1, then I install jira 2, still point out to database 1 ? what would be happening ?
kind of reminding one servant two masters, but not at the same time :-D
Due to limited source, I only get one database for testing, so I wonder 'recycling' , however, should I contact DBA to wrap out whole database before I config it in another jira ?
For older versions of Jira, yes, it was a disaster. Both of them would be unable to write issues correctly and their indexes fail rapidly. If you left them long enough, with active users, you'd get a completely corrupt database.
Newer versions of Jira try to prevent the corruption - the first one to connect writes a record into a table which tells other installations that the database is in use, so they just shut down with an error saying the database is already in use by a previous Jira.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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