Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix topic closed normally but still call
closeFencedTopicForcefully
. (
apache#15196) (apache#15202) Co-authored-by: druidliu <[email protected]> Fixes apache#15196. ### Motivation If broker having conf `topicFencingTimeoutSeconds`>0, a topic is trigged closed and closed normally, `closeFencedTopicForcefully` should not be called. ### Modifications Cancel fenced topic monitoring task if topic close normally, which cancel running `closeFencedTopicForcefully`. ### Verifying this change - [ ] Make sure that the change passes the CI checks. This change added tests and can be verified as follows: - Add `org.apache.pulsar.broker.service.PersistentTopicTest#testTopicCloseFencingTimeout` ### Does this pull request potentially affect one of the following parts: *If `yes` was chosen, please highlight the changes* - Dependencies (does it add or upgrade a dependency): (yes / no) - The public API: (yes / no) - The schema: (yes / no / don't know) - The default values of configurations: (yes / no) - The wire protocol: (yes / no) - The rest endpoints: (yes / no) - The admin cli options: (yes / no) - Anything that affects deployment: (yes / no / don't know) ### Documentation Check the box below or label this PR directly. Need to update docs? - [ ] `doc-required` - [x] `no-need-doc` - [ ] `doc` - [ ] `doc-added` (cherry picked from commit e4a8de1)
- Loading branch information