useV2WireProtocol for bookkeeper autorecovery #12311
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
Currently we only set
bookkeeperUseV2WireProtocol=true
on Pulsar brokers to enforce brokers to use v2 protocol to avoid GC issues introduced by protobuf.However, we don’t set this setting on autorecovery, and the default value is false, Hence AutoRecovery will use v3 protocol.
We'd better set
useV2WireProtocol=true
in autorecovery in the helm chartsModifications
Set
useV2WireProtocol=true
in autorecovery.