-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track client connection information reported from zookeeper cons/stat command #10475
Comments
Just confirming that Since we haven't yet had historical tracking of this data, it's hard to say 100% for sure how we'd use it. But sure looks useful. @pmoust may have some thoughts here as well
|
@matschaffer I'm finishing the PR to add
|
Wonder if @stejacks or @mattfield might know offhand. If not we can always go code-diving 🏊 |
This comes from Netty's Channel InterestOps, as seen in ZooKeeper's That said, please note exactly how I think you can name the field |
Yes, that makes sense. That field is the interest information on either NIO or Netty, hence the code is a bit obscure - interest on either the selectorkey or channel respectively. I've found it most useful in debugging during overload conditions (zk server will disable recv in order to put backpressure on clients). "interestOps" seems fine, it might be helpful to break out the values into human readable form, but unfortunately ZK itself is not doing a good job here. |
This should be fixed now that #11070 is merged. |
#8938 was originally opened to address the need to track zkid from the
stat
command. Thesrvr
command also exposes this data and tracking is implemented in #10341To get a more complete view of zookeeper activity we'd also like to track the
cons
(or possibly the first part ofstat
, still need to confirm) output which displays information about all connected clients.The text was updated successfully, but these errors were encountered: