Raul Gutierrez Segales created ZOOKEEPER-1788:
-------------------------------------------------
Summary: Support clientID field on connection requests
Key: ZOOKEEPER-1788
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1788
Project: ZooKeeper
Issue Type: Improvement
Reporter: Raul Gutierrez Segales
Priority: Minor
I suspect it's very common for deployments to have a wide variety of client
libraries (different versions/languages) connecting to a given cluster.
It would be handy to have a way to identify clients via a clientID (akin to
HTTP's User-Agent header). This could be implemented in
ZooKeeperServer#processConnectRequest [1] and be fully backwards compatible.
The clientID could then be kept with the corresponding ServerCnxn instance and
be used for better logging (or stats expose through 4-letter commands).
The corresponding client side change would be to expose API to set the clientID
on each connection handler (and by default it could be something like "zk java
$version", "zk c $version", etc).
Thoughts?
[1]
https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java#L797
--
This message was sent by Atlassian JIRA
(v6.1#6144)
