You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/04/15 02:36:06 UTC

[GitHub] [druid] gianm commented on issue #9701: DruidLeaderClient always thinks the first node returned from DruidNodeDiscovery is the leader

gianm commented on issue #9701: DruidLeaderClient always thinks the first node returned from DruidNodeDiscovery is the leader
URL: https://github.com/apache/druid/issues/9701#issuecomment-613781088
 
 
   The problem happens with `DruidLeaderClient.goAsync`, which lets callers provide their own HttpResponseHandler, but doesn't contain the leader-following logic. It is used by the Druid SQL system tables so they can avoid materializing the entire response for the APIs they are hitting (which could be large). Perhaps the best fix is that it should learn how to follow leaders.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org