[Issue 9496] fix logic in ManagedLedgerWriter when config threadNum >= ledgerNum #9497
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.
fix #9496
fix logic in ManagedLedgerWriter when config threadNum >= ledgerNum
Modifications
if threadNum >= ledgerNum.
allocate ledger repeat among threads.
origin logic may have thread without ledger and got an exception.
Verifying this change
build and run
./pulsar-perf managed-ledger -e 3 -w 2 -o 10000 --threads 20 -r 100000 -s 2048 -zk localhost:2181
no exception in stdlog
Documentation