Repository navigation
Double service announcement from coordinator #369
Description
It looks like under certain conditions the coordinator can announce itself twice in service discovery. The indexing overlord may have a similar issue, since its announcement process is similar.
We observed something like:
1- Coordinator #1 logged ZK "SUSPENDED" followed by "Unannouncing service"
2- Coordinator #2 became leader and logged "Announcing service"
3- Coordinator #1 logged ZK "LOST" followed by "RECONNECTED"
Then some time later:
4- Coordinator #2 logged ZK "SUSPENDED" followed by "Unannouncing service" followed by ZK "RECONNECTED"
5- Coordinator #1 became leader and logged "Announcing service"
At this point Coordinator #1 was leader and was registered twice in service discovery. It appears that it probably did not successfully unannounce its service in step 1.
Activity
tarekrached commentedon Feb 7, 2014
It would be totally sweet if this worked right.
github-actions commentedon May 13, 2023
This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.
github-actions commentedon Jun 10, 2023
This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.