Version: NiFi 1.11.x
Noticed a behavior where for this version of NiFi, when the remote url is a GSLB, it doesn't recognize when a host is removed from a GSLB until the processor is stopped. Any idea why? Any ideas for a solution?
Kind of an update: A jank workaround was to force the Connection to close, but it's not the best solution. Looking to see why the client is ignoring the DNS TTL.
This is a behaviour inherited from Java. Java caches DNS resolved names internally.
You can adjust the cache TTL value by specifying the corresponding Java property during NiFi startup.
Please see a description of the property here: https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-jvm-ttl.html
Can you share your settings?
I've attempt to set the above in the java.security file and in the bootstrap I set the runtime variables as