Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-922

enable faster timeout of sessions in case of unexpected socket disconnect

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • server
    • None

    Description

      In the case when a client connection is closed due to socket error instead of the client calling close explicitly, it would be nice to enable the session associated with that client to time out faster than the negotiated session timeout. This would enable a zookeeper ensemble that is acting as a dynamic discovery provider to remove ephemeral nodes for crashed clients quickly, while allowing for a longer heartbeat-based timeout for java clients that need to do long stop-the-world GC.

      I propose doing this by setting the timeout associated with the crashed session to "minSessionTimeout".

      Attachments

        1. ZOOKEEPER-922.patch
          3 kB
          Camille Fournier

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            fournc Camille Fournier
            fournc Camille Fournier

            Dates

              Created:
              Updated:

              Slack

                Issue deployment