eolivelli opened a new pull request #9232:
URL: https://github.com/apache/pulsar/pull/9232
### Motivation
BookKeeper 4.12 introduces the 'Opportunistic Striping' feature.
In BK terms 'striping' happens when EnsembleSize is greater than
WriteQuorumSize, in this mode the entries are distributed round robin over a
set of bookies, in order to achieve better performances as you can use the
resources of more bookies.
For instance in a small HA cluster, with only 3 bookies, you must run Pulsar
with 2-2-2 replication parameters
(EnsembleSize=2,WriteQuorumSize=2,AckQuorumSize=2).
You cannot set EnsembleSize=3 (and thus use 'striping') because in case of
temporary outage of a single bookie the BK client is not able to create an
ensemble with 3 bookies.
With Opportunistic Striping you can use 3-2-2 and when the system is fully
up-and-running with 3 bookies then you go with striping, but during single
bookie outages (like during reconfigurations/updates) you fall back to 2-2-2.
This is not about consistency or durability, it is only about having the
ability to get the most out of your bookkeeper cluster.
### Modifications
Add new configuration option
### Verifying this change
- the change add new tests
### Does this pull request potentially affect one of the following parts:
*If `yes` was chosen, please highlight the changes*
- Dependencies: no
- The public API: no
- The schema: no
- The default values of configurations: no
- The wire protocol: no
- The rest endpoints: no
- The admin cli options: no
- Anything that affects deployment: no
- ### Documentation
- Does this pull request introduce a new feature? yes
- If yes, how is the feature documented? JavaDocs and default
configuration files
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
