Michael Xu commented on ZOOKEEPER-829:

hi everyone,

i plan on taking this on my plate. 

patrick and i spoke over irc, there are issues with the current method of 
logging in and closing client id's for the purposes of explicitly expiring 

being able to have explicit control over sessions is a very desirable feature 
for those doing testing with zookeeper.

i'll put some code in SessionTracker.java, that adds to DataTree.java on 
session creation on the cluster leader to create a /zookeeper/sessions/<id> and 
set a watch on it. clients may write a "close" to a zknode, which the server 
will acknowledge by removing the session. 

> Add /zookeeper/sessions/* to allow inspection/manipulation of client sessions
> -----------------------------------------------------------------------------
>                 Key: ZOOKEEPER-829
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-829
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Todd Lipcon
> For some use cases in HBase (HBASE-1316 in particular) we'd like the ability 
> to forcible expire someone else's ZK session. Patrick and I discussed on IRC 
> and came up with an idea of creating nodes in /zookeeper/sessions/<session 
> id> that can be read in order to get basic stats about a session, and written 
> in order to manipulate one. The manipulation we need in HBase is the ability 
> to write a command like "kill", but others might be useful as well.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to