Redis medium
What is the primary technical responsibility of the Redis Sentinel subsystem in a highly available production environment?
- A Managing the sharding of data across multiple hash slots to allow for infinite horizontal scalability.
- B Detecting Master failures and orchestrating the automatic promotion of a Replica to new Master.
- C Periodically compressing RDB snapshots and archiving them to long-term storage partitions on S3.
- D Acting as a transparent network proxy that identifies and blocks malicious SQL and NoSQL injection.
Answer: B. Detecting Master failures and orchestrating the automatic promotion of a Replica to new Master.
Sentinel is the 'health monitor'. It manages the failover process automatically so developers don't have to manually update connection strings or promote nodes during a middle-of-the-night server crash.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- If the Redis memory limit is reached, what specific behavior is exhibited by the `allkeys-lru` eviction policy?
- What is the defining characteristic of a Redis 'Set' data type compared to a standard Redis 'List'?
- In the context of Redis messaging, what is the functional definition of the 'Pub/Sub' feature?
- How does the Redis background snapshotting process (`BGSAVE`) leverage the operating system's `fork()` mechanism to minimize memory overhead?
- Why does Redis proactively disconnect a Pub/Sub client that exhibits high 'output buffer' usage relative to its ingestion rate?
- How does a 'Sorted Set' (ZSET) manage its internal membership and ordering differently from a plain Set?