You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Vishal Khandelwal (JIRA)" <ji...@apache.org> on 2016/06/20 12:53:05 UTC

[jira] [Created] (ZOOKEEPER-2449) Refresh the invalid host which got unknownhostexception during connection in StaticHostProvider

Vishal Khandelwal created ZOOKEEPER-2449:
--------------------------------------------

             Summary: Refresh the invalid host which got unknownhostexception during connection in StaticHostProvider
                 Key: ZOOKEEPER-2449
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2449
             Project: ZooKeeper
          Issue Type: Improvement
            Reporter: Vishal Khandelwal
            Priority: Minor


As per the current logic if a host has "UnknownHostException" during zookeeper client object connection and it is never refreshed after that. Incase host comes back, this class won't try to connect it back.

Ideally in StaticHostProvider.next we end of the list is reached then all of the host in connection string should be tested and refreshed again. That way incase host comes back and object stays for a longer duration, realtime status can be updated and client can take advantage of that



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