[jira] [Commented] (ZOOKEEPER-1356) Avoid permanent caching of server IPs in the client

["Brice Dutheil (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132497#comment-15132497 ] 

Brice Dutheil commented on ZOOKEEPER-1356:
------------------------------------------

[~nehanarkhede] Could this ticket ZOOKEEPER-1506 be helpful ?

> Avoid permanent caching of server IPs in the client 
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-1356
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1356
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.3.4, 3.4.2
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>
> Relevant conversation on the dev mailing list - https://email.corp.linkedin.com/owa/redir.aspx?C=87f3d1e78c96438c8115e450f410d010&URL=http%3a%2f%2fmarkmail.org%2fmessage%2f3vzynx6rgurubf3p%3fq%3dPerforming%2bno%2bdowntime%2bhardware%2bchanges%2bto%2ba%2blive%2bzookeeper%2bcluster%2blist%3aorg%252Eapache%252Ehadoop%252Ezookeeper-dev
> Basically, the client caches the list of server IPs internally and maintains that list for the entire lifetime of the client. This limits the ability to remove/change a server node from a zookeeper cluster, without having to restart every client. Also, two levels of IP caching, one in the JVM and one in the zookeeper client code seems unnecessar.
> It would be ideal to provide a config option that would turn off this IP caching in the client and re-resolve the host names during the reconnect. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)