Optimize bookie decommission check wait interval #4070
Merged
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.
Motivation
When triggering one bookie decommission, the bookie check max interval is 10 minutes.
It has the following issues:
validateBookieIsNotPartOfEnsemble
23140
, but after 10 minutes, the ledger count is 2984. But the first check interval is calculated based on23140
.Changes
sleepTimePerLedger
from 10 seconds to 3 secondsvalidateBookieIsNotPartOfEnsemble
check in the first round before going to sleep to keep the count of ledgers waiting for replication accurate.