-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fix mqbblp::RecoveryManager: Clear sync peer promptly #589
base: main
Are you sure you want to change the base?
Conversation
Can ignore IncoreCSL unit test failure. Will be fixed in another branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This logs source
twice (instead of primarySyncPeer
):https://bbgithub.dev.bloomberg.com/BMQ/blazingmq-mirror/blob/85fa14b429195474314a4fc1675b5bc923099a6e/src/groups/mqb/mqbblp/mqbblp_storagemanager.cpp#L813
Can we document/comment somewhere how do RecoveryManager_PrimarySyncContext::primarySyncInProgress()
and RecoveryManager_PrimarySyncContext::syncPeer()
relate? What are the scenarios when one is 0
and the other is not (if any)?
Signed-off-by: Yuan Jing Vincent Yan <[email protected]>
Signed-off-by: Yuan Jing Vincent Yan <[email protected]>
Signed-off-by: Yuan Jing Vincent Yan <[email protected]>
Signed-off-by: Yuan Jing Vincent Yan <[email protected]>
313caff
to
f4cbbb6
Compare
@dorjesinpo Added some explanation. Hope that clears things up. |
See internal ticket 178057288
Clearing sync peer promptly prevents this failure condition to trigger when the sync peer node goes down after sync with that peer is already complete. Otherwise, we will call
onPartitionPrimarySyncStatus(partitionId, -1 /* status */);
and fail this assert later on because primary is already active.