[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Koch updated ZOOKEEPER-14:
---------------------------------

    Description: 
Moved from SourceForge to Apache.
http://sourceforge.net/tracker/index.php?func=detail&aid=1948097&group_id=209147&atid=1008544

There should be a better connection between connect timeout, ping timeout, and 
session timeout. On the Java client it is sessionTimeout/hostsList.length. On 
the C client it's just the readTimeout. There is also an arbitrary delay when 
we find that all the hosts are down.

We should come up with a good consistent story for the connect timeout. Since 
we leave sessionTimeout/3 ms for recovery from a down server, it seems most 
reasonable to have something like sessionTimeout/(3*hostsList.length).

  was:
Moved from SourceForge to Apache.
http://sourceforge.net/tracker/index.php?func=detail&aid=1948097&group_id=209147&atid=1008544

    
> Connect timeouts not calculated properly
> ----------------------------------------
>
>                 Key: ZOOKEEPER-14
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-14
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client, java client
>            Reporter: Patrick Hunt
>            Assignee: Benjamin Reed
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1948097&group_id=209147&atid=1008544
> There should be a better connection between connect timeout, ping timeout, 
> and session timeout. On the Java client it is 
> sessionTimeout/hostsList.length. On the C client it's just the readTimeout. 
> There is also an arbitrary delay when we find that all the hosts are down.
> We should come up with a good consistent story for the connect timeout. Since 
> we leave sessionTimeout/3 ms for recovery from a down server, it seems most 
> reasonable to have something like sessionTimeout/(3*hostsList.length).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to