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

Gtid_Slave_Pos is not reported equal using show variables or show all slaves status

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.0, 10.1, 10.2.9, 10.2
    • 10.2
    • Replication
    • None

    Description

      Definition of doc about show all slaves status

      Gtid_Slave_Pos GTID of the last event group replicated on a slave server, for each replication domain, as stored in the gtid_slave_pos system variable. Returned with SHOW ALL SLAVES STATUS only.

      MariaDB [(none)]> select version();
      +----------------------------------------+
      | version()                              |
      +----------------------------------------+
      | 10.2.9-MariaDB-10.2.9+maria~jessie-log |
      +----------------------------------------+
       
      MariaDB [(none)]> show global variables like 'gtid_sl%';
      +----------------+-----------------+
      | Variable_name  | Value           |
      +----------------+-----------------+
      | gtid_slave_pos | 0-3232261191-29 |
      +----------------+-----------------+
      

      pager grep -i gtid_slave_pos
      PAGER set to 'grep -i gtid_slave_pos'
      MariaDB [(none)]> show all slaves status\G
                     Gtid_Slave_Pos: 0-3232261190-30
      

      A list of binlog events in the slave that show some writes happen on it on top of replication events
      https://pastebin.com/Mvg7uCKv

      Not using multi domain
      Not using strict mode

      Attachments

        Activity

          People

            Elkin Andrei Elkin
            stephane@skysql.com VAROQUI Stephane
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.