Controller模式,重启后,发现主从不同步,报错信息:Failed to find a consistent point between masterEpoch: #7674
onejimmyboy
started this conversation in
General
Replies: 5 comments 1 reply
-
看着主备之间的epochFileCheckpoint中的epoch无法对齐,但这些日志无法查出报错的原因。有办法稳定复现吗? |
Beta Was this translation helpful? Give feedback.
1 reply
-
我这边部署5.1.3版本的controller+broker集群,一主一从的模式下,也出现了这个问题 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
我这5.2.0也有这个问题 |
Beta Was this translation helpful? Give feedback.
0 replies
-
好像是长时间不同步,会有这个问题,epoch数据会被清理。可以换个数据目录,作为新节点同步。理论上代码里应该handle这种情况 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
version:5.1.3
集群形态:嵌入式部署Controller,共3节点(1个节点部署Controller+namesrv,另外两个节点都部署namesrv+Controller+broker)。
现象,集群搭建的时候,服务正常,主从同步。之后发送消息,重启服务后,主从无法同步,信息如下:
疑问:报错的信息是Failed to find a consistent point between masterEpoch,
1)这个报错信息代表的是什么意思?导致报错的原因?
2)如何修复呐?自己有尝试重启,但是依然无法修复
Beta Was this translation helpful? Give feedback.
All reactions