[
https://issues.apache.org/jira/browse/ZOOKEEPER-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Xu updated ZOOKEEPER-829:
---------------------------------
Attachment: zookeeper-829.diff
hi everyone,
here is a patch for this issue.
the server creates zknodes at /zookeeper/sessions with the sessionID as the
name (NOT hex-encoded, uses base-10 representation of the sessionID ).
Any client writing anything to a session node causes the session to be expired.
I will write unit tests when I get a chance, but I'd like feedback on
design-wise what may need to be changed in order to include it officially.
Likely, the next step will be making a test mode specifically for
zookeeperserver so clients can use this functionality of managing sessions
themselves.
michael
> 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
> Attachments: zookeeper-829.diff
>
>
> 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.
