-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 10.10
-
Fix Version/s: HOTFIX_10.10, 2021.x, 11.x
-
Component/s: Streams
-
Epic Link:
-
Story Points:3
It is common to have:
- broker with a dynamic IP -> we should not cache the DNS lookup
- broker name that resolves with multiple IPs -> in case of failure we should try the next IP
Confluent recommends the following configuration:
At java level:
java.security.Security.setProperty(“networkaddress.cache.ttl” , “30"); java.security.Security.setProperty(“networkaddress.cache.negative.ttl” , “0");
At Kafka consumer and producer level with:
consumer.client.dns.lookup="use_all_dns_ips" producer.client.dns.lookup="use_all_dns_ips"
The java configuration will be global and it changes the dns cache from infinite to 30s which should be ok.