PIP-161 Exclusive Producer: ability to fence out an existing Producer (ExclusiveWithFencing mode) - #15488
Conversation
|
@eolivelli:Thanks for your contribution. For this PR, do we need to update docs? |
|
It changed the protocol and public API, I'm not sure if we need a proposal for it. |
|
@momo-jun a soft reminder: here is a PR w/ doc-required label, could u pls follow up? Thanks |
merlimat
left a comment
There was a problem hiding this comment.
👍
I don't like ExclusiveWithFencing too much though I cannot come up with a better suggestion.
For the "doc-required" label, it's needed to remember updating the docs. eg: https://pulsar.apache.org/docs/en/concepts-messaging/#access-mode
Finally, as @mattisonchao mentioned, this is touching public API so it would be good to have a PIP discussion and vote.
|
@eolivelli I can add docs for this PR as soon as it is approved/merged. If you'd like to do it, feel free to ping me for review. Either way works for me. |
83c14f0 to
42808ea
Compare
I have updated that section, thanks for the reminder. |
Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
|
thank you @Anonymitaet. I have committed your suggestion |
|
@merlimat @mattisonchao @Anonymitaet please take another look |
|
/pulsarbot rerun-failure-checks |
|
/pulsarbot rerun-failure-checks |
2 similar comments
|
/pulsarbot rerun-failure-checks |
|
/pulsarbot rerun-failure-checks |
Motivation
Currently (in 2.10) we have two ways of creating a Exclusive Producer: Exclusive and WaitForExclusive.
We are missing a mode in which the new Producer fences out any existing producer, allowing to apply Optimistic Locking pattern.
Linked PIP: #15528
Modifications
Verifying this change
This change added tests.