You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2023. It is now read-only.
Ideally, ZooKeeper client instances should be instrumentable with metrics; specifically, each request type (e.g. "create", "set", "getACL", etc.) should be timed to measure request latency etc.
This is problematic because:
ZooKeeper is a class, there is no interface that would allow us to naturally extend the API.
The constructor of ZooKeeper initialises the thread-pool and socket connections for the client, which prevents us from writing tests for any sub-classes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ideally,
ZooKeeper
client instances should be instrumentable with metrics; specifically, each request type (e.g. "create", "set", "getACL", etc.) should be timed to measure request latency etc.This is problematic because:
ZooKeeper
is aclass
, there is nointerface
that would allow us to naturally extend the API.ZooKeeper
initialises the thread-pool and socket connections for the client, which prevents us from writing tests for any sub-classes.The text was updated successfully, but these errors were encountered: