Cassandra easy
When a client sends a write request to any node in a Cassandra cluster, what is the temporary role that node assumes for that specific request?
- A The 'Ultimate Authority', permanently locking all other nodes until the write is complete.
- B The 'Shadow Master', assuming leadership for the entire cluster for exactly one hour.
- C The 'Coordinator', responsible for managing the data transfer to replicas and returning a consolidated result to the client.
- D The 'Archivist', immediately moving the data to cold storage.
Answer: C. The 'Coordinator', responsible for managing the data transfer to replicas and returning a consolidated result to the client.
The 'Coordinator' is not a dedicated node; *any* node can take this role. It acts as the 'Request Manager'—it checks the cluster map, sends the data to the correct replica nodes, waits for enough success signals, and then tells the client 'Success'.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- In a Cassandra Keyspace, what does a 'Replication Factor of 3' specifically guarantee for your data redundancy?
- Unlike a Leader-Follower architecture (like MySQL or Redis), how does Cassandra maintain high availability within its node cluster?
- Cassandra Query Language (CQL) looks similar to SQL. What is a fundamental SQL feature that CQL does NOT support to ensure distributed performance?
- What is the critical architectural function of the 'Partition Key' in a Cassandra table?
- Apache Cassandra is fundamentally designed as which architectural category of NoSQL database?
- An extreme financial trading application requires 'Batch' sync for the Commit Log. What is the fundamental throughput limitation introduced by this setting?