Cassandra easy
How do nodes in a Cassandra cluster maintain awareness of the health and 'Up/Down' status of fellow nodes without a central master?
- A They all connect to a centralized 'Health Server' that monitors every node with a heartbeat.
- B They use a 'Gossip Protocol', where nodes randomly exchange state information with a few peers, allowing knowledge to spread like a virus.
- C They use a shared Wi-Fi network that automatically detects when a node loses its signal.
- D An administrator must manually update a YAML file on every node whenever a peer is added or removed.
Answer: B. They use a 'Gossip Protocol', where nodes randomly exchange state information with a few peers, allowing knowledge to spread like a virus.
Gossip is a peer-to-peer communication protocol. Every second, a node contacts a few random peers to share info about itself and others it has heard from. This 'Epidemic Algorithm' ensures that the entire cluster (even thousands of nodes) eventually reaches 'Convergance' on the state of the ring.
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?