Instead of editing java.security properties, JVM allows to specify a property 
file in command line. All the properties will be appended to the default 
(/global) security properties. This way configuration remain local to the 
application.

# An alternate java.security properties file may be specified
# from the command line via the system property
#
#    -Djava.security.properties=<URL>
#
# This properties file appends to the master security properties file.
# If both properties files specify values for the same key, the value
# from the command-line properties file is selected, as it is the last
# one loaded.
#

-anoop
________________________________
From: Will Lauer <[email protected]>
Sent: Thursday, March 21, 2019 10:37 AM
To: [email protected]
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 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, Verizon Media
o: 217-255-4264
m: 508-561-6427


On Thu, Mar 21, 2019 at 9:14 AM Don Bowman <[email protected]> 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>
>

Reply via email to