Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We have two raft cluster,
A cluster IP is
A1:7082,A2:7082,A3:7082
B cluster master ip is
B1:7082,B2:7082,B3:7082
When we start A cluster we use a wrong config
A1:7082,A2:7082,B3:7082
After we start the cluster we found we use wrong config.
But this info has been write to raft-meta.conf.
Then after we restart A cluster, when client connect to A cluster.
It connect to A cluster follower then return the cached leader address, the leader peer id is 3, but in the meta conf, the peer rpc link is B3:7082.
Then cause it connect to cluster B.
Its caused by RaftPeer object equal only compare peerId cause it won't refresh raft-meta.conf
Attachments
Attachments
Issue Links
- links to