-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The peer to be destroyed is inconsistent with the current peer. #666
Comments
When the number of stores is greater than the number of copies, the pd schedules region copies to maintain cluster stores size balance. Frequent deletion of scheduled peers can easily cause this issue. |
When a peer is destroyed and a raft msg handler is created using the previously cached peer inbox. This issue will occur If use this msg handler to handle messages. When the received message is appended to the corresponding peer, we can check whether the peer is destroyed, and if it is, we update the peer inbox in the cache.
unistore/tikv/raftstore/peer_worker.go Lines 219 to 227 in 792ba34
unistore/tikv/raftstore/peer_worker.go Lines 209 to 217 in 792ba34
|
The text was updated successfully, but these errors were encountered: