Zixuan Liu
Zixuan Liu
/pulsarbot rerun-failure-checks
/pulsarbot rerun-failure-checks
@hanmz Please rebase master branch.
> At least we need to recover the partition metadata for such orphan partitions. Currently it's impossible: > > ```shell > > admin topics create-partitioned-topic my-topic -p 1 > 2025-04-25T19:45:14,373+0800...
> > This is difficult because we can not obtain the maximum partition index. > > We can list all non-partitioned topics of the `-partition-` pattern and find the maximum...
> I agree with this plan. Our cluster has been running for many years, so there are likely quite a few topics with metadata errors. @crossoverJie If the broker automatically...
> > Do this during topic creation (e.g., via admin topics create-partitioned-topic) or at runtime? > > Topic creation, or `BrokerService#getTopic` on a non-partitioned topic whose name ends with `-partition-`....
> I don't think create missing topic partition metadata in runtime is OK, as @nodece says, it would introduce unpredictable consequences. Actually, I think add a new config is the...
> Then support creating missed partitions via admin API for such cases could be the solution. Currently the create-missed-partitions API does not work. @BewareMyPower `admin topics create-partitioned-topic my-topic -p 1`...
Alternative approach: #4588