Druid assumes the network layer handles whatever tuning is needed regarding DNS resolution or IP routing. In general this means making sure you have your java settings correct (see https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-jvm-ttl.html for a related article).
On Thu, Mar 21, 2019 at 7:14 AM Don Bowman <d...@agilicus.com> wrote: > What is the expectation around dns and druid? Specifically, when overlord > started, it resolved (correctly) my kafka cluster nodes. > A little bit later I made a change which changed their IP. But overlord > continues to use that originally resolved IP. > > Is there a way to force the refresh? > Should it be re-resolving on a connection failure? > > [Consumer clientId=consumer-6, groupId=kafka-supervisor-bebmfiod] > Connection to node 2 (kafka-2.kafka-headless.kafka/*10.60.8.24*:9092) could > not be established. Broker may not be available. > > $ kubectl -n kafka get pods -o=wide NAME READY STATUS RESTARTS AGE IP NODE > NOMINATED NODE kafka-0 1/1 Running 0 20m 10.60.7.45 > gke-noctest-default-pool-51f579ce-ztgf <none> kafka-1 1/1 Running 0 20m > 10.60.1.48 gke-noctest-default-pool-8674014d-p008 <none> kafka-2 1/1 > Running 0 20m *10.60.8.48* gke-noctest-default-pool-3aa530af-cztp <none> > kafka-health-check-5d5b457566-2k8lf 1/1 Running 0 20m 10.60.2.47 > gke-noctest-default-pool-8674014d-rxbn <none> >
