After upgrading to Pulsar 2.11.0, we encountered an issue where we were unable to immediately query non-persistent topics that were created in Pulsar. This behavior was unexpected as everything was functioning properly prior to this release. We have identified two known issues ([1] and [2]) that are currently being tracked for resolution.
However, even after the release of Pulsar 3.0 LTS, we are still experiencing the same behavior. Therefore, I would like to initiate a discussion regarding this issue. Specifically, I would like to understand why Pulsar is dropping the queries on non-persistent topics and explore potential solutions that would require minimal changes to the codebase in the 3.0 LTS version. [1]: https://github.com/apache/pulsar/issues/19316 [2]: https://github.com/apache/pulsar/issues/19493
