ken
> We are hitting this bug in pulsar version 3.0.12 which uses bookkeeper client 4.16.6. Is there any update on the fix? no update. This fix has been used in...
@codelipenghui @congbobo184 Can you help review this pr?
> Great catch @TakaHiR07. What is the current impact of this in Pulsar & Bookkeeper (which is using PulsarLedgerManager in the Pulsar distribution of Bookkeeper)? One impact is all the...
> > > Great catch @TakaHiR07. What is the current impact of this in Pulsar & Bookkeeper (which is using PulsarLedgerManager in the Pulsar distribution of Bookkeeper)? > > >...
> @TakaHiR07 Are you still working on this? Sorry for forget this work. If needing, I can finish this in a few day.
> Can we add some tests? @shoothzj @horizonzy Have done. Can you help review again. Thx
> Can you please start the discussion on the [[email protected]](mailto:[email protected]) mailing list? Done, can see here, https://lists.apache.org/thread/ltdls9r55h70mdxc0z8k5qzvzw48nb6d
> Which logic could cause this issue ? @Technoboy- restart broker with version-3.0.x. Restart broker-1, and after a few time restart broker-2. When load topic and getTopicPolicy on broker-1, the...
> How could the latest code cause the issue ? I'm not understand You can see the code in branch-3.0. Latest code is a bit different, the concurrent case is...
> So it's better to fix it to branch-3.0, for the master branch, I don't think it's needed. @Technoboy- I think it is better to also fix in master branch....