jihoonson opened a new issue #9701: DruidLeaderClient always thinks the first node returned from DruidNodeDiscovery is the leader URL: https://github.com/apache/druid/issues/9701 ### Affected Version 0.18.0 ### Description This bug seems to be introduced in https://github.com/apache/druid/pull/9481. Before this PR, `DruidLeaderClient` used `ServerDiscoverySelector` to find the leader. Since only the leader Overlord and Coordinator announce themselves, `ServerDiscoverySelector` could return the current leader to `DruidLeaderClient`. But now, `DruidLeaderClient` picks up the first node returned from `DruidNodeDiscovery` which knows all announced nodes. This breaks the internal redirection of `DruidLeaderClient`.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
