Community
Q&A
Crowd
Questions
Will Disabling Autocommit in the MySQL Database Adversely Affect Crowd?

Will Disabling Autocommit in the MySQL Database Adversely Affect Crowd?

We have a Crowd 5.0 instance and a Jira 9.1 instance connected to it. Their databases are both hosted in the same MySQL instance.

We recently upgraded to MySQL 8.0 and everything seems to be functioning normally. However, in the documentation here, it specifies that Jira requires the "autocommit" field in the my.cnf to be set to false. In the documentation here, it does not specify to disable that setting explicitly when configuring the database for Crowd.

Will having autocommit turned off in the database adversely affect Crowd in any way?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes

Answer accepted

Welcome to the Atlassian Community!

No, it needs to be set that way, otherwise you may find you get deadlocks in the database, which will stop people from logging in. It won't happen often, and the symptom is a hung login, which the users can refresh the page and probably be able to log in again, but it can happen.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you very much!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Was this helpful?

Thanks!

Crowd

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Will Disabling Autocommit in the MySQL Database Adversely Affect Crowd?

1 answer

1 accepted

Comments for this post are closed

Was this helpful?

Thanks!

TAGS

Atlassian Community Events