Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 39.4Mb
PDF (A4) - 39.4Mb
PDF (RPM) - 38.7Mb
HTML Download (TGZ) - 11.1Mb
HTML Download (Zip) - 11.1Mb
HTML Download (RPM) - 9.8Mb
Man Pages (TGZ) - 213.5Kb
Man Pages (Zip) - 322.6Kb
Info (Gzip) - 3.6Mb
Info (Zip) - 3.6Mb
Excerpts from this Manual

25.12.11.8 The replication_group_member_stats Table

This table shows statistical information for MySQL Group Replication members. It is populated only when Group Replication is running.

The replication_group_member_stats table has the following columns:

  • CHANNEL_NAME

    Name of the Group Replication channel.

  • VIEW_ID

    Current view identifier for this group.

  • MEMBER_ID

    The member server UUID. This has a different value for each member in the group. This also serves as a key because it is unique to each member.

  • COUNT_TRANSACTIONS_IN_QUEUE

    The number of transactions in the queue pending conflict detection checks. Once the transactions have been checked for conflicts, if they pass the check, they are queued to be applied as well.

  • COUNT_TRANSACTIONS_CHECKED

    The number of transactions that have been checked for conflicts.

  • COUNT_CONFLICTS_DETECTED

    The number of transactions that have not passed the conflict detection check.

  • COUNT_TRANSACTIONS_ROWS_VALIDATING

    Number of transactions which can be used for certification, but have not been garbage collected. Can be thought of as the current size of the conflict detection database against which each transaction is certified.

  • TRANSACTIONS_COMMITTED_ALL_MEMBERS

    The transactions that have been successfully committed on all members of the replication group, shown as GTID Sets. This is updated at a fixed time interval.

  • LAST_CONFLICT_FREE_TRANSACTION

    The transaction identifier of the last conflict free transaction which was checked.

TRUNCATE TABLE is not permitted for the replication_group_member_stats table.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.