liangyepianzhou commented on issue #13793:
URL: https://github.com/apache/pulsar/issues/13793#issuecomment-1064122775
The cause is we use a future to wait the operation of
`deletePartitionedTopicAsync` and `deleteNamespaceBundleAsync`.
And we hope `deletePartitionedTopicAsync` executes before
`deleteNamespaceBundleAsync` but `deleteNamespaceBundleAsync` executes before
`deleteTopicAsync` in fact .
Background:
1. `deleteNamespaceBundleAsync` will trigger `Topic::close` which will
fence topic.
2. So TopicFencedException will be cause when t `Topic::delete`
3. Both `Topic::delete` and `Topic::close` will check if fence and
fence the topic. But the check of `Topic::close` is
`(!isClosingOrDeleting || closeWithoutWaitingClientDisconnect) `and
`closeWithoutWaitingClientDisconnect == true`.
4. So `deletePartitionedTopicAsync` executes before
`deleteNamespaceBundleAsync` is no problem.
--
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]
