, as it is the last
# one loaded.
#
-anoop
From: Will Lauer
Sent: Thursday, March 21, 2019 10:37 AM
To: dev@druid.apache.org
Subject: Re: dns lookups cached for kafka?
See the documentation for java.net.InetAddress. By default, Java caches DNS
results, and may be caching them more
See the documentation for java.net.InetAddress. By default, Java caches DNS
results, and may be caching them more than you expect. This is controllable
via some properties that you can set on the command line.
Will
*Will Lauer*
Senior Principal Architect
Audience and Advertising Reporting,
I believe so. That's what I do
On Thu, Mar 21, 2019 at 8:52 AM Don Bowman wrote:
> On Thu, 21 Mar 2019 at 11:48, Charles Allen .invalid>
> wrote:
>
> > Druid assumes the network layer handles whatever tuning is needed
> regarding
> > DNS resolution or IP routing. In general this means making
On Thu, 21 Mar 2019 at 11:48, Charles Allen
wrote:
> 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
>
>
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
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