[jira] [Commented] (ZOOKEEPER-1436) Add ZOO_TIMED_OUT_STATE sesion event to notify client about timeout during reconnection

["Hadoop QA (Commented) (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on ZOOKEEPER-1436:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12520346/ZOOKEEPER-1436.patch
  against trunk revision 1302736.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 9 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1017//console

This message is automatically generated.
                
> Add ZOO_TIMED_OUT_STATE sesion event to notify client about timeout during reconnection
> ---------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1436
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1436
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.4.3
>            Reporter: Thawan Kooburat
>              Labels: patch
>         Attachments: ZOOKEEPER-1436.patch
>
>
> The zookeeper c client knows how long its session will last, and periodically pings in order to keep that session alive. However, if it loses connection, it hops from ensemble member to ensemble member trying to reform the session - even after the session timeout expires.
> This patch at a new session event (ZOO_TIMED_OUT_STATE) that notifies the user that the session timeout has passed, and we have been unable to reconnect. The event is one-shot per disconnection and get generated from the C-client library itself. The server has no knowledge of this event.  
> Example use cases:
> 1. Client can try to reconnect to a different set of observers if it unable to connect to the original set of observers.
> 2. Client can quickly stop acting as an active server, since other server may already taken over the active role while it is trying to reconnect. 

--
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