Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 38.5Mb
PDF (A4) - 38.5Mb
PDF (RPM) - 33.3Mb
HTML Download (TGZ) - 8.1Mb
HTML Download (Zip) - 8.2Mb
HTML Download (RPM) - 7.0Mb
Man Pages (TGZ) - 134.2Kb
Man Pages (Zip) - 190.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

25.11.11.10 The replication_group_member_stats Table

This table shows statistical information for replication group members.

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

    Identifier for this member; same as the server UUID.

  • COUNT_TRANSACTIONS_IN_QUEUE

    Number of transactions pending certification

  • COUNT_TRANSACTIONS_CHECKED

    Number of transactions already certified by this member.

  • COUNT_CONFLICTS_DETECTED

    Number of transactions that were negatively certified.

  • COUNT_TRANSACTIONS_VALIDATING

    Number of transactions with which one can execute certification with them, but have not been garbage collected.

  • TRANSACTIONS_COMMITTED_ALL_MEMBERS

    Set of stable group transactions.

  • LAST_CONFLICT_FREE_TRANSACTION

    Latest transaction certified without conflicts.

  • COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE

    Number of waiting transactions this member has received from the group.

  • COUNT_TRANSACTIONS_REMOTE_APPLIED

    Number of transactions this member has received from the group and applied.

  • COUNT_TRANSACTIONS_LOCAL_PROPOSED

    Number of transactions this member originated and sent to the group.

  • COUNT_TRANSACTIONS_LOCAL_ROLLBACK

    Number of transactions this member originated that were rolled back by the group.

The replication_group_member_stats table has these indexes:

  • None

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.