c.remove_instance("192.168.200.136:3306") The instance will be removed from the InnoDB Cluster. * Waiting for instance '192.168.200.136:3306' to synchronize with the primary... ** Transactions replicated ###################################################= 98% ERROR: The instance '192.168.200.136:3306' was unable to catch up with cluster transactions. There might be too many transactions to apply or some replication error. In the former case, you can retry the operation (using a higher timeout value by setting the global shell option 'dba.gtidWaitTimeout'). In the later case, analyze and fix any replication error. You can also choose to skip this error using the 'force: true' option, but it might leave the instance in an inconsistent state and lead to errors if you want to reuse it. ERROR: MYSQLSH 51141: Replication thread not in expected state Traceback (most recent call last): File "<string>", line 1, in <module> mysqlsh.Error: Shell Error (51141): Cluster.remove_instance: Replication thread not in expected state 在删除仲裁节点时,是不是要特殊的语法。 |
reddey
2024-5-27 15:34:14
| ||
一个学艺不精的国产数据库爱好者
|
||
yejr
2024-5-27 16:05:11
| ||
reddey
2024-5-27 16:49:23
| ||
一个学艺不精的国产数据库爱好者
|
||
合作电话:010-64087828
社区邮箱:greatsql@greatdb.com