GitHub user lhotari added a comment to the discussion: Issues with Topic-Level Policies after Cluster Restart in Pulsar 3.0.5
> Is this a known bug in Pulsar? If so, in which version was it fixed? Yes. * https://github.com/apache/pulsar/issues/24553 * https://github.com/apache/pulsar/issues/24436 The problem might be caused by BookKeeper data loss issue (https://github.com/apache/bookkeeper/pull/4607) fixed in BookKeeper release 4.16.7 / 4.17.2 included since Pulsar 3.0.13, 3.3.8 and 4.0.6 releases. The latest supported Pulsar releases are 3.0.15, 4.0.9 and 4.1.2, so it's recommend to upgrade to one of the supported versions. https://pulsar.apache.org/download/ > Are there any temporary workarounds besides disabling topic-level policies > entirely? That might be a viable option in certain cases. Please check the issues for possible workaround. > Currently, we're considering reverting to namespace-level policies. Are there > other recommended solutions to maintain topic-level Policy requirements while > avoiding this issue? Make sure to run an up-to-date version of Pulsar. There are hundreds of bug fixes since 3.0.5 release. If you run on an old version, you might be running into issues that have already been addressed. GitHub link: https://github.com/apache/pulsar/discussions/24930#discussioncomment-15077129 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
