MySQL Error number: MY-011726; Symbol: ER_GRP_RPL_MEMBER_STATS_INFO; SQLSTATE: HY000 报错 故障修复 远程处理

文档解释

Error number: MY-011726; Symbol: ER_GRP_RPL_MEMBER_STATS_INFO; SQLSTATE: HY000

Message: Flow control – update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%d

MySQL Error MY-011726, Symbol ER_GRP_RPL_MEMBER_STATS_INFO, or SQLSTATE HY000, is an error that occurs when attempting to access the group replication member stats information that doesn’t exist. This error is caused by a missing or corrupted group replication member stats data file.

Error My-011726, ER_GRP_RPL_MEMBER_STATS_INFO, or SQLSTATE HY000, is typically encountered when trying to access the group replication member stats information. This is a data file that contains the current state of the group replication server members. The data file contains the IP address, the port, the protocol version, and other information. When this file is missing or corrupted, the error occurs.

The first step in addressing this error is to identify what is causing the error. To do this, you can review the MySQL error log and look for any entries related to this error. Once you have identified what is causing the error you need to address the issue. This can be done by restoring the group replication member stats data file from a backup or recreating the file with the correct data.

If restoring or recreating the group replication member stats file does not resolve the issue, there may be other underlying problems with the group replication server. For example, there could be an issue with the connection between members or a problem with the replication server configuration. If these issues are present, they should be addressed before attempting to access the group replication member stats information.

In summary, My-011726, Symbol ER_GRP_RPL_MEMBER_STATS_INFO, or SQLSTATE HY000, is an error that is caused by a missing or corrupted group replication member stats data file. To resolve this issue, you should identify what is causing the error, restore or recreate the data file, and address any underlying issues with the group replication server.