ERM
redis
runtime_error
ai_generated
partial
集群节点超时，可能检测到脑裂
ERR Cluster node timeout exceeded, possible split-brain detected
ID: redis/cluster-node-timeout-split-brain
75%修复率
82%置信度
1证据数
2023-08-20首次发现
版本兼容性
| 版本 | 状态 | 引入 | 弃用 | 备注 |
|---|---|---|---|---|
| 6.2 | active | — | — | — |
| 7.0 | active | — | — | — |
| 7.2 | active | — | — | — |
根因分析
集群节点在 cluster-node-timeout 内未响应，导致可能的脑裂场景，多个节点假定为主节点角色。
English
A cluster node failed to respond within cluster-node-timeout, leading to a potential split-brain scenario where multiple nodes assume master roles.
官方文档
https://redis.io/docs/latest/operate/oss_and_stack/management/scaling/解决方案
-
在所有健康主节点上运行 'CLUSTER FORGET <node-id>' 移除无响应节点，网络恢复后重新加入。
-
配置 sentinel monitor 使用多数节点作为法定人数，防止脑裂。示例：'sentinel monitor mymaster 127.0.0.1 6379 2'。
无效尝试
常见但无效的做法:
-
70% 失败
Delays detection but does not prevent network partitions; can worsen split-brain.
-
85% 失败
May cause data loss if RDB/AOF not synced; does not resolve underlying network issues.
-
95% 失败
Split-brain can cause inconsistent data; manual intervention required.