-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-26832 Avoid repeated releasing of flushed wal entries in AsyncF… #4281
Conversation
…SWAL#syncCompleted
🎊 +1 overall
This message was automatically generated. |
if (epoch(epochAndState) != epochWhenSync || writerBroken(epochAndState)) { | ||
LOG.warn("Got a sync complete call after the writer is broken, skip"); | ||
return; | ||
} |
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.
LGTM. I have a little concern about the blocked sync futures that can not be returned by syncFailed and also be ignored by syncCompleted. But since all will be returned eventually, it's not a big problem.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
…SWAL#syncCompleted (apache#4281) Signed-off-by: Xiaolin Ha <haxiaolin@apache.org> (cherry picked from commit 4f491fd) (cherry picked from commit 9355506) Change-Id: I4535a76306e32c8928e2bb2c0c9d6162119739db
…SWAL#syncCompleted