curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shevek (JIRA)" <>
Subject [jira] [Commented] (CURATOR-8) Possible mishandling of connection timeouts on large/shooty clusters
Date Fri, 29 Mar 2013 23:33:16 GMT


Shevek commented on CURATOR-8:

Tempted to say that we don't care about session timeout in that routine; if the Ensemble is
responsible for updating the host list, then the client connectTimeoutMs is "The amount of
time a user application allows a connection request to remain pending before delivering an
Exception to the caller."
> Possible mishandling of connection timeouts on large/shooty clusters
> --------------------------------------------------------------------
>                 Key: CURATOR-8
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client
>            Reporter: Shevek
>            Assignee: Jordan Zimmerman
> 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:

View raw message