You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Tyler Monahan (JIRA)" <ji...@apache.org> on 2018/04/30 20:25:01 UTC

[jira] [Created] (KAFKA-6839) ZK session retry with cname record

Tyler Monahan created KAFKA-6839:
------------------------------------

             Summary: ZK session retry with cname record
                 Key: KAFKA-6839
                 URL: https://issues.apache.org/jira/browse/KAFKA-6839
             Project: Kafka
          Issue Type: Bug
    Affects Versions: 1.1.0
            Reporter: Tyler Monahan


I have a 3 node kafka cluster setup in aws that talks to a 3 node zk cluster behind an elb. I am giving the kafka instances a dns cname record that points to the aws elb which is another cname record pointing to two A records. When the aws elb cname record changes the two A records it is pointing at and kafka trys to reconnect to zk after losing a session it uses the old A records and not the new ones so the reconnect attempt fails. There appears to be some kind of caching instead of using the record that is set in the config file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)