[pulsar-zookeeper-utils] Fix Updating Rack Info Dynamically #8844
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
When the value of "/bookies" in ZooKeeper is changed, Brokers are notified of the change.
After the notification to Brokers, only one of the two BookKeeper clients that Brokers have seems to reflect the change.
Two BookKeeper clients that Brokers have
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/ManagedLedgerClientFactory.java
Line 81 in ac0c6e4
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/schema/BookkeeperSchemaStorage.java
Line 105 in 102fa9d
The client of
BookkeeperSchemaStorage
don't seems to reflect the change.The cause is that
ZkBookieRackAffinityMapping#onUpdate
don't run.I confirmed that I change ZkBookieRackAffinityMapping instances to use same
ZooKeeperDataCache
andZkBookieRackAffinityMapping#onUpdate
works.Modification
ZkBookieRackAffinityMapping#setConf
tobookieMappingCache
updateRacksWithHost()