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

manual modification proof policy for mysql.gtid_slave_pos

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5, 10.6, 10.11, 11.1(EOL), 11.2(EOL), 11.4
    • None
    • Replication
    • None

    Description

      While MDEV-15393 describes a use case of modifying mysql.gtid_slave_pos via mysqldump
      that leads to replication failure, a similar concern exists for abusive changes made by a user.
      Preferably direct sql updates to mysql.gtid_slave_pos should not be allowed when replication is under way. And when they are done the gtid/replication slave states must become in sync with them. Specifically should mysql.gtid_slave_pos be manually inserted with a record having a new max of sub_id column, any new record that will be automatically inserted should have its column value greater than the maximum.

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            Unassigned Unassigned
            Elkin Andrei Elkin
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.