Conversation
SongOf
force-pushed
the
fix/broker-ownership-cache-generation-race
branch
from
July 22, 2026 14:38
1f7e054 to
8f4d0b6
Compare
…Ownership and lock-expiry cleanup
SongOf
force-pushed
the
fix/broker-ownership-cache-generation-race
branch
from
July 23, 2026 19:05
8f4d0b6 to
724a40a
Compare
# Conflicts: # pulsar-broker/src/main/java/org/apache/pulsar/broker/service/BrokerService.java # pulsar-broker/src/test/java/org/apache/pulsar/broker/service/BrokerServiceTest.java
…d TLS material provider plugin interface (apache#25890)
… orderly consumer scaling (apache#26208)
…p-client-api SPI modules (apache#26222)
…to-creation is disabled (apache#26279)
… are no context attributes (apache#26285)
…lsar-txn-consumable for peek messages (apache#26073)
…aned delayed-delivery buckets (apache#26309)
…acementPolicyLedgerFragmentsOnRack (apache#26308)
…r instead of cast the class (apache#26298)
…lowed the cluster to access (apache#26276)
… factory integration (core migration) (apache#26282)
…ary glibc baseline (apache#26315)
…t provider is registered (apache#26154) Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…servlet additional servlets (apache#26444)
…ar-function-go (apache#26446) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ets auto-scale policy (apache#26434)
… paths and restore configured ordering (apache#26462)
…ng broker entry metadata (apache#26464)
…ange units and static stats state (apache#26466)
…ust memory parameters (apache#26468)
…ient (apache#26480) ### Motivation `pulsar-perf` was migrated to the V5 client API in apache#25887 and `pulsar-client` in apache#25917, so every subcommand of both tools now drives the V5 SDK. Pulsar 5.0 does not deprecate ordinary (non-scalable) topics and the v4 client remains fully supported, so it is still useful to drive the CLI tools with the v4 client: for benchmark results comparable across broker versions (the v4 commands can also target pre-5.0 brokers, which the V5 SDK cannot talk to at all), and for testing the v4 client and ordinary topics without the V5 SDK in the path. The migration also left a set of options that are still accepted but no longer do what they say, with no way to get the behaviour back — round-robin partition routing and the outstanding-message limits on `produce`, the real subscription types and the receiver-queue knobs on `consume`, the v4 `Reader` and its `<ledgerId>:<entryId>` start position on `read`, the v4 transaction coordinator on `transaction`, KeyValue schemas and non-durable subscriptions on `pulsar-client`, and `loadConf` for `client.conf` keys without a dedicated CLI flag. ### Modifications Each command is split into an abstract base holding everything that is not client-specific, plus two thin sibling subclasses that bind the client types — the existing V5 command and a new v4 one: ``` PerformanceProducerBase -> PerformanceProducer / PerformanceProducerV4 (produce-v4) PerformanceConsumerBase -> PerformanceConsumer / PerformanceConsumerV4 (consume-v4) PerformanceReaderBase -> PerformanceReader / PerformanceReaderV4 (read-v4) PerformanceTransactionBase -> PerformanceTransaction / PerformanceTransactionV4 (transaction-v4) AbstractCmdProduce -> CmdProduce / CmdProduceV4 (produce-v4) AbstractCmdConsumeCommand -> CmdConsume / CmdConsumeV4 (consume-v4) AbstractCmdReadCommand -> CmdRead / CmdReadV4 (read-v4) ``` `PulsarClientTool` builds a second, lazily-supplied v4 `ClientBuilder` for the `*-v4` commands; it keeps `loadConf` and accepts `http://` service URLs. `pulsar-shell` picks the new `pulsar-client` commands up for free, and both tools' `gen-doc` / `generate_documentation` render them. New subcommands only. The V5 commands keep their behaviour apart from a few deliberate fixes that the split surfaced (the `ProducerSocket` send/ack ordering and its `close()` null guard, the transaction receive-failure path), plus some added "use the `-v4` command" pointers on existing warnings — all listed in the PR description. ### Verifying this change Covered by `PulsarPerfTestToolTest`, `PerformanceV4CommandsTest`, `PerformanceTransactionV4Test`, `CmdV4CommandsTest`, `PulsarClientToolTest` (including the three KeyValue cases disabled by apache#25917, now re-enabled against `produce-v4`), and new `produce-v4` / `consume-v4` / `read-v4` cases in the `PerfToolTest` integration test.
…ad of under the wrapper write lock (apache#26463)
…ck allocation hotspot (apache#26500)
…xMetadataInterceptor isn't configured (apache#26497)
SongOf
force-pushed
the
fix/broker-ownership-cache-generation-race
branch
from
September 9, 2026 16:50
b9ae6cc to
0adab8c
Compare
…the ownership barrier without recursion
SongOf
force-pushed
the
fix/broker-ownership-cache-generation-race
branch
from
September 9, 2026 16:51
0adab8c to
2166893
Compare
…sting setter instead of reflection
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…Ownership and lock-expiry cleanup
Fixes #xyz
Main Issue: #xyz
PIP: #xyz
Motivation
Modifications
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes