You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2013/09/25 05:31:02 UTC
[jira] [Resolved] (CURATOR-8) Possible mishandling of connection
timeouts on large/shooty clusters
[ https://issues.apache.org/jira/browse/CURATOR-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jordan Zimmerman resolved CURATOR-8.
------------------------------------
Resolution: Fixed
Added a warning if session timeout is less than connection timeout
> Possible mishandling of connection timeouts on large/shooty clusters
> --------------------------------------------------------------------
>
> Key: CURATOR-8
> URL: https://issues.apache.org/jira/browse/CURATOR-8
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.0.0-incubating
> Reporter: Shevek
> Assignee: Jordan Zimmerman
> Fix For: 2.3.0
>
>
> See CURATOR-7 for background.
> ConnectionState.checkTimeouts resets the connection if the session timeout has expired, whether or not we ever had a session. If one has a large, shooty cluster with a short session timeout and a long connection timeout, this might reset the host list pointer to zero every sessionTimeoutMs, never letting it connect to a valid, available host towards the end of the list. On the other hand, if it is an assertion that sessionTimeout > connectionTimeout always, then the min() call is not required and the ifelse should read "else if (elapsed > connectionTimeoutMs)" instead of just "else".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira