aymkhalil commented on PR #19097: URL: https://github.com/apache/pulsar/pull/19097#issuecomment-1411025708
> Have you considered the double-check: use cached policies to decide on eligibility as without your changes, check again with refresh right before managedLedgerFactory.asyncOpen call in the BrokerService, fail if ns.deleted. I didn't explicitly, the approach was to trace all http calls that touches the ns policy ([here](https://github.com/apache/pulsar/pull/19097#discussion_r1059203687)) so we cover more cases, but not cases where this could add unnecessary overhead (hence the distinction between http vs binary calls). But you made me think, actually the automatic topic creation triggered by a producer is actually on the binary protocol path so I either have to make all `isAllowAutoTopicCreationAsync` use the refresh API, or consider limiting the scope to the ML open async as you proposed... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
