[fix][broker] Skip topic.close during unloading if the topic future fails with ownership check, and fix isBundleOwnedByAnyBroker to use ns.checkOwnershipPresentAsync for ExtensibleLoadBalancer

[heesung-sn]

Fixes #20157

Motivation

#20157 found that the ExtensibleLoadManagerImplTest init step, unloading the test namespace often fails.

Modifications

• Skip topic.close during unloading if the topic future fails with ownership check. If the unloading(not transfer) happens in the middle of topic creation, the topic creation might fail because of the ownership check failure. In this case, we need to skip unloading that topic, not to fail the unload command.
• Fix isBundleOwnedByAnyBroker to use ns.checkOwnershipPresentAsync for ExtensibleLoadBalancer. Currently, isBundleOwnedByAnyBroker is unnecessarily selecting a new owner broker, if no owner is found. We should simply check ownership, instead.
• Skip assignment command events in UnloadManager.handlEvent. UnloadManager should not complete the inflight jobs from the Owned event from assignment commands. This could result in returning unload command too fast, although the unloading is still in progress.

Verifying this change

• Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: