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
{{ message }}
This repository has been archived by the owner on Oct 7, 2024. It is now read-only.
Now if exhibitor list can't be refreshed, than AWSExhibitorAddressProvider will query data from master_exhibitors. But it's much better to query data from AWS to get new exhibitor list from lb name.
And of course it's better not to start kafka instances if there are no exhibitor instances.
Maybe it's better not to start kafka if exhibitor list is empty.
The text was updated successfully, but these errors were encountered:
Why is this a good idea? I thought that one of the goals of exhibitor was to discover other zookeepers and coordinate them. I thought that it would be a reliable source of information.
@rcillo In this issue I am trying to reference exactly one situation: all the exhibitors are suddenly disappeared.
It means, that during normal work we are using zookeeper list provided by exhibitor API. But in case of catastrophic disaster (no exhibitor instances available) we need to use aws api to refresh exhibitor list, instead of trying to connect to outdated instances.
Now if exhibitor list can't be refreshed, than AWSExhibitorAddressProvider will query data from master_exhibitors. But it's much better to query data from AWS to get new exhibitor list from lb name.
And of course it's better not to start kafka instances if there are no exhibitor instances.
Maybe it's better not to start kafka if exhibitor list is empty.
The text was updated successfully, but these errors were encountered: