Gr_all_consensus_proposals_count

在该节点上发起并终止的所有提案的总和。Sum of all proposals that were initiated and terminated on this node.

Gr_all_consensus_time_sum

在此节点上开始并完成的所有共识轮次的总耗时。通过将此值与Gr_all_consensus_proposals_count进行比较，我们可以确定给定的共识时间是否存在上升趋势，这可能表明存在问题。The total elapsed time for all consensus rounds started and finished on this node. By comparing this value with Gr_all_consensus_proposals_count, we can determine whether a given consensus time has an upward trend, which may signal a problem.

Gr_certification_garbage_collector_count

认证垃圾回收运行的次数。The number of times certification garbage collection has been run.

Gr_certification_garbage_collector_time_sum

认证垃圾收集所用时间的微秒总和。Sum of the times in microseconds taken by certification garbage collection.

Gr_consensus_bytes_received_sum

从以此节点为目标的组节点接收的所有套接字级字节的总和。The sum of all socket-level bytes received from group nodes having this node as a destination.

Gr_consensus_bytes_sent_sum

从此节点发出并发送到所有（其他）组节点的所有套接字级字节的总和。这里报告的数据比发送的消息更多，因为它们被复用并发送到每个成员。Sum of all socket-level bytes originating on this node that were sent to all (other) group nodes. More data is reported here than for sent messages, since they are multiplexed and sent to each member.

例如，如果我们有一个包含三个成员的组，并且发送一个 100 字节的消息，那么该值计入 300 字节，因为我们向每个节点发送 100 字节。For example, if we have a group with three members and we send a 100-byte message, this value accounts for 300 bytes, since we send 100 bytes to each node.

Gr_control_messages_sent_count

此成员发送的控制消息数量。Number of control messages sent by this member.

Gr_control_messages_sent_bytes_sum

该成员发送的控制消息所使用字节数的总和；这是传输时的数据大小。Sum of the number of bytes used in control messages sent by this member; this is the on-the-wire size.

Gr_control_messages_sent_roundtrip_time_sum

该成员发送的控制消息往返时间（以微秒为单位）的总和；往返时间是从消息发送到发送者接收消息之间的时间。此值应提供群组大多数成员（包括发送者）发送和接收控制消息之间的时间。Sum of the round-trip times in microseconds for control messages sent by this member; a round trip is measured between the sending and the delivery of the message on the sender. This should provide the time between sending and delivery of control messages for the majority of the members of the group, including the sender.

Gr_data_messages_sent_bytes_sum

该成员发送的数据消息使用的字节总数；这是传输中的大小。Sum in bytes used by data messages sent by this member; this is the on-the-wire size.

Gr_data_messages_sent_count

这是该成员发送的事务数据消息的数量。This is the nmber of transaction data messages sent by this member.

Gr_data_messages_sent_roundtrip_time_sum

该成员发送的数据消息的往返时间总和（以微秒为单位）；往返时间是在发送方发送消息和消息被投递之间测量的。这应该提供大多数组成员（包括发送方）发送和投递数据消息之间的时间。Sum of the round-trip times in microseconds for data messages sent by this member; a round trip is measured between the sending and the delivery of the message on the sender. This should provide the time between sending and delivery of data messages for the majority of the members of the group, including the sender.

Gr_empty_consensus_proposals_count

在此节点上发起并终止的所有空提议轮的总和。Sum of all empty proposal rounds that were initiated and terminated on this node.

Gr_extended_consensus_count

该节点已启动的完整三相轮次的次数。如果该数字随时间增长，这意味着至少有一个节点在响应提议时遇到问题，可能是由于运行缓慢或网络问题。诊断此类问题时，请将此值与 Performance Schema replication_group_communication_information 表中的 count_member_failure_suspicions 列一起使用。The number of full 3-phase rounds that this node has initiated. If this number grows over time, it means that at least one node is having problems answering to proposals, either due to something it to run slowly, or to network issues. Use this value together with the count_member_failure_suspicions column of the Performance Schema replication_group_communication_information table when diagnosing such issues.

Gr_last_consensus_end_timestamp

上次共识提案被批准的时间，以时间戳格式显示。这可以作为组进展缓慢或已停止的一个指标。The time when the last consensus proposal was approved, in a timestamp format. This can be an indicator whether the group is making slow progress, or has halted.

Gr_total_messages_sent_count

该节点发送到组的高层消息数量。这些消息是从 API 接收到的，用于向组提出提案。XCom 批处理机制会将这些消息批量处理并一起提出。此变量显示的值反映了批处理之前的消息数量。The number of high-level messages sent by this node to the group. These are the messages received from the API for proposing to the group. The XCom batching mechanism batches these messages and proposes them all together. The value shown for this variable reflects the number of messages prior to batching.

Gr_transactions_consistency_after_sync_count

在等待主节点的事务被提交时，二级节点上等待开始的事务数量，主节点事务的 group_replication_consistency 设置为 AFTER 或 BEFORE_AND_AFTER。Number of transactions on secondaries that waited to start, while waiting for transactions from the primary with group_replication_consistency equal to AFTER or BEFORE_AND_AFTER to be committed.

Gr_transactions_consistency_after_sync_time_sum

二级节点中事务在开始之前等待主节点事务提交的微秒总时间，这些主节点事务的 group_replication_consistency 设置为 AFTER 或 BEFORE_AND_AFTER。Sum of the times in microseconds that transactions on secondaries waited on transactions from the primary with group_replication_consistency equal to AFTER or BEFORE_AND_AFTER to be committed, before starting.

Gr_transactions_consistency_after_termination_count

使用 group_replication_consistency 设置为 AFTER 或 BEFORE_AND_AFTER 执行的事务数量。The number of transactions executed with group_replication_consistency equal to AFTER or BEFORE_AND_AFTER.

Gr_transactions_consistency_after_termination_time_sum

在使用 group_replication_consistency 设置为 AFTER 或 BEFORE_AND_AFTER 执行的事务交付与其他组成员确认事务已准备好的时间（微秒）之和。Sum of the time in microseconds between delivery of the transaction executed with group_replication_consistency equal to AFTER or BEFORE_AND_AFTER, and acknowledgement by the other group members that the transaction is prepared.

此值不包括事务发送往返时间。This value does not include transaction send roundtrip time.

Gr_transactions_consistency_before_begin_count

使用 group_replication_consistency 设置为 BEFORE 或 BEFORE_AND_AFTER 执行的事务数量。Number of transactions executed with group_replication_consistency equal to BEFORE or BEFORE_AND_AFTER.

Gr_transactions_consistency_before_begin_time_sum

成员在执行事务之前，其组复制应用通道被消耗的等待时间（以微秒为单位）的总和，当 group_replication_consistency 等于 BEFORE 或 BEFORE_AND_AFTER 时。Sum of the time in microseconds that the member waited until its group replication applier channel was consumed before executing the transaction with group_replication_consistency equal to BEFORE or BEFORE_AND_AFTER.