You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Damien Diederen (Jira)" <ji...@apache.org> on 2021/05/20 09:31:00 UTC

[jira] [Resolved] (ZOOKEEPER-3970) Enable ZooKeeperServerController to expire session

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

Damien Diederen resolved ZOOKEEPER-3970.
----------------------------------------
    Fix Version/s: 3.7.1
                   3.8.0
       Resolution: Fixed

Issue resolved by pull request 1505
[https://github.com/apache/zookeeper/pull/1505]

> Enable ZooKeeperServerController to expire session
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-3970
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3970
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: server, tests
>            Reporter: Michael Han
>            Assignee: Michael Han
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.8.0, 3.7.1
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> This is a follow up of ZOOKEEPER-3948. Here we enable ZooKeeperServerController to be able to expire a global or local session. This is very useful in our experience in integration testing when we want a controlled session expiration mechanism. This is done by having session tracker exposing both global and local session stats, so a zookeeper server can expire the sessions in the controller. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)