We are running JIRA 6.0.3 and Stash 2.6. Each connects to its own MySQL database which is on a separate machine.
We have a database server where we run the MySQL databases for our Atlassian products.
All of this is duplicated for DEV vs PROD environments.
We would like to upgrade Stash, but the documentation for Stash 2.7 indicates that we must change the settings of the MySQL database server in a way that contradicts the settings required for JIRA.
I asked Atlassian about this, and they indicated that "JIRA and Stash behave this way", and that I should see if I could get help via asking the question at answers.atlassian.com
We would prefer to run our databases on the same database server, rather than deploy a separate machine for each individual database. I guess I am asking if there is a way to get around this problem without placing the JIRA and Stash databases on separate machines (i.e. separate MySQL installations).
If we determine that separate servers are required then should we take the hit now and place the Confluence database on a separate machine as well in case this type of conflict happens between Confluence and either JIRA or Stash in the future?
In the official Connecting Stash to MySQL document we state:
If MySQL is using binary logging, configure the database to use a binary logging format of either
I have tweaked that KB article to match our official document - so we will avoid conflict of information. Hence, you should be fine with the current "binlog_format=row" on the JIRA database.
Do open a ticket with us in case you have problem and thanks for pointing this out.
Atlassian Support - Stash
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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