mon: remove the redundant min_last_epoch_clean judge in PGMap #9861
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the end of the apply_incremental function, no matter what happens the min_last_epoch_clean must be 0. Signed-off-by:song baisen <song.baisen@zte.com.cn>
|
Huh! Good patch! LGTM (pending test) |
|
@liewegas @athanatos @yuriw Thanks to all! I also have this pr #9749 Is there anyone like to review it? |
|
@songbaisen i will take a look at it. |
|
@tchaikov OK, Thanks very much to you ! 👍 👍 👍 👍 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mon: remove the redundant min_last_epoch_clean judge in PGMap
In the end of the apply_incremental function, no matter what
happens the min_last_epoch_clean must be 0.
Signed-off-by:song baisen song.baisen@zte.com.cn