Zookeeper medium
ZooKeeper provides 'Four Letter Word' (4LW) commands like `mntr` and `stat`. How are these traditionally accessed by administrators?
- A Sent as plain-text commands over the standard client port (2181) using tools like `nc` or `telnet`.
- B Encapsulated within a persistent gRPC session and authenticated via a cluster-wide private certificate.
- C Embedded directly into the metadata header of a mock write transaction to the `/config/monitoring` Znode.
- D Broadcast via UDP to the specialized 8080 monitoring port and captured by an external sidecar process.
Answer: A. Sent as plain-text commands over the standard client port (2181) using tools like `nc` or `telnet`.
These 'Four Letter Words' are the standard way to monitor ZK. e.g., `echo stat | nc localhost 2181` returns the version, mode (leader/follower), and connection count.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What is the primary technical function of a ZooKeeper 'Watch'?
- A system administrator increases `jute.maxbuffer` to 5MB on every ZooKeeper server to store large configuration objects. However, write operations larger than 1MB still fail. What is the most likely cause?
- By default, `forceSync` is enabled. If you disable it, what trade-off are you making?
- If the specific ZooKeeper node a client is connected to crashes, what should the client do?
- Which cluster configuration has *worse* availability: A 3-node cluster or a 4-node cluster? (Assuming simple majority quorum)
- According to the CAP Theorem, how is ZooKeeper classified?