You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched in the issues and found nothing similar.
Version
pulsar: master
auto-recovery: inline in pulsar.
Minimal reproduce step
Use pulsar-admin to set rack info.
Observe the AutoRecovery log, it show that aware the newest rack info.
Restart AutoRecovery, it didn't aware the rack info, stepdown to default rack info /default-region/default-rack
Analyze:
The pulsar works well; the AutoRecovery works badly, the difference is RegistrationClient.
In pulsar, it uses PulsarRegistrationClient to resolve the address; in AutoRecovery, it uses ZKRegistrationClient to resolve the address.
The ZKRegistrationClient only resolves the address registered in zookeeper. PulsarRegistrationClient resolved the address directly, didn't care whether the address was registered in zookeeper or not.
When parsing the rack info, it will resolve the address first, then use the resolved result to build rack info mapping. When AutoRecovery start, it will parse rack info first. At the same time, the ZKRegistrationClient didn't receive the registered
address info, so ZKRegistrationClient can't parse rack info incorrectly.
What did you expect to see?
AutoRecovery also aware the rack info after restart.
What did you see instead?
AutoRecovery didn't aware the rack info after restart.
Anything else?
No response
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Version
pulsar: master
auto-recovery: inline in pulsar.
Minimal reproduce step
/default-region/default-rack
Analyze:
The pulsar works well; the AutoRecovery works badly, the difference is RegistrationClient.
In pulsar, it uses PulsarRegistrationClient to resolve the address; in AutoRecovery, it uses ZKRegistrationClient to resolve the address.
The ZKRegistrationClient only resolves the address registered in zookeeper. PulsarRegistrationClient resolved the address directly, didn't care whether the address was registered in zookeeper or not.
When parsing the rack info, it will resolve the address first, then use the resolved result to build rack info mapping. When AutoRecovery start, it will parse rack info first. At the same time, the ZKRegistrationClient didn't receive the registered
address info, so ZKRegistrationClient can't parse rack info incorrectly.
What did you expect to see?
AutoRecovery also aware the rack info after restart.
What did you see instead?
AutoRecovery didn't aware the rack info after restart.
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: