Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4964

Support MySQL Replication using Global Transaction IDs

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Database - MySQL
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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

            Unassigned Unassigned
            jpalacios Juan Palacios (Inactive)
            Votes:
            10 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: