Fixes not owned bundles got selected when broker overloading

[kezhuw]

Motivation

Fixes not owned bundles got selected when broker overloading

Modifications

Filters out not owned bundles in finding candidate bundles for unloading.

Verifying this change

This change added tests and can be verified as follows:

• Adds test to ensure only owned bundles got selected when broker overloading.

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

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

• Does this pull request introduce a new feature? (no)

[kezhuw]

run java8 tests

[sijie]

@kezhuw thank you for the fix. although just out of curiosity, at which condition, bundles will be inconsistent with bundleData? Have you encountered this issue in your production?

[kezhuw]

@sijie I found this issue in reading through pulsar not production. What this issue reporting is not-owned-by bundles, eg. bundles that were owned by other brokers, were selected due to broker overloading, not inconsistent between LocalBrokerData.getBundles and LoadData.getBundleData.

I think the testing code is somewhat confusing, may be better to bind ownerless bundles to a not overloaded broker ?

[kezhuw]

@sijie I have add a fixup commit to refine testing code, and now it should be more clearly that the testing code is trying to assert only owned bundles got selected (this is the commit title of the first commit 2b9a2b0). This fixup commit should be squash out or rebase to first commit in merging if this pr got approved.

[kezhuw]

run cpp tests

[kezhuw]

run java8 tests
run cpp tests

[sijie]

@merlimat @rdhabalia PTAL

[sijie]

@merlimat @rdhabalia PTAL