-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Overview
MySQL uses Global Transaction Identifiers as part of their replication mechanism. See http://dev.mysql.com/doc/refman/5.6/en/replication-gtids.html
Issue
Customers hitting this issue will see a message on the application logs similar to the one below:
2015-07-07 17:06:16,123 WARN [http-bio-7990-exec-15] <user> @1Q5I8BYx1026x359x1 1wn1yo6 <IP>,<IP> "DELETE /projects/<SLUG>/repos/<SLUG> HTTP/1.1" o.h.h.s.TemporaryTableBulkIdStrategy unable to drop temporary id table after use [When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1.]
That happens because of ENFORCE_GTID_CONSISTENCY = 1 on the MySQL database.
Workaround
Turn off ENFORCE_GTID_CONSISTENCY on the database.
Note: This precludes the use of Google Cloud SQL, which enforces the use of GTID
- is related to
-
BSERV-3385 Enable Oracle Golden Gate replication
- Gathering Interest
- mentioned in
-
Page Failed to load
Form Name |
---|
Hibernate, which is used for all database interactions in Bitbucket Server, does not support GTIDs (See HHH-9289) Running Bitbucket Server connected to MySQL with GTIDs enabled will not be possible until such time as either:
Pragmatically, rewriting our entire database layer to not use Hibernate purely to support GTIDs on MySQL, a configuration used by a very small subset of installs on one of our 7 supported RDBMSes, is not a viable product decision.
Best regards,
Bryan Turner
Atlassian Bitbucket