Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-35627

mysql.gtid_slave_pos gets really big

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.10
    • None
    • Galera, Replication
    • None

    Description

      This issue occurred in the migration of a Galera Cluster from 10.4 to 10.11.10. To migrate, I created a new cluster running 10.11.10.

      Each cluster had 3 nodes. The replication ran from node B to node B, from the old cluster to the new cluster. Each node has binary logging enabled and log_slave_updates enabled.

      On the new cluster, on nodes A and C (where no asynchronous replication was running!) the mysql.gtid_slave_pos table has many rows and is 3.9GB large.

      This not blocks me from setting up an asynchronous replica from nodes A and C. I expect this to block SST as well when nodes A or C are the donor. Is there a safe way to fix this?

      Thank you,

      Attachments

        Issue Links

          Activity

            People

              janlindstrom Jan Lindström
              michaeldg Michaël de groot
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.