Pre-General Availability Draft: 2017-12-16
Each member in a replication group certifies and applies transactions received by the group. Statistics regarding the certifier and applier procedures are useful to understand how the applier queue is growing, how many conflicts have been found, how many transactions were checked, which transactions are committed everywhere, and so on.
table provides group-level information related to the
certification process, and also statistics for the transactions
received and originated by each individual member of the
replication group. The information is shared between all the
server instances that are members of the replication group, so
information on all the group members can be queried from any
member. Note that refreshing of statistics for remote members is
controlled by the message period specified in the
option, so these can differ slightly from the locally collected
statistics for the member where the query is made.
Table 21.1 replication_group_member_stats
The name of the Group Replication channel.
The current view identifier for this group.
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.
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.
The number of transactions that have been checked for conflicts.
The number of transactions that did not pass the conflict detection check.
The current size of the conflict detection database (against which each transaction is certified).
The transactions that have been successfully committed on all members of the replication group. This is updated at a fixed time interval.
The transaction identifier of the last conflict free transaction checked.
The number of transactions that this member has received from the replication group which are waiting to be applied.
The number of transactions that this member has received from the replication group which have been applied.
The number of transactions that this member originated and sent to the replication group for coordination.
The number of transactions that this member originated that were rolled back after being sent to the replication group.
These fields are important for monitoring the performance of the members connected in the group. For example, suppose that one of the group’s members is delayed and is not able to keep up to date with the other members of the group. In this case you might see a large number of transactions in the queue. Based on this information, you could decide to either remove the member from the group, or delay the processing of transactions on the other members of the group in order to reduce the number of queued transactions. This information can also help you to decide how to adjust the flow control of the Group Replication plugin.