Elasticsearch hard
How did the 7.0+ 'Cluster Coordination' subsystem replace the legacy `minimum_master_nodes` setting to prevent split-brain scenarios?
- A It uses a hardcoded list of node IP addresses in the `elasticsearch.yml` file.
- B Dynamic Voting Configuration: The cluster maintains a set of nodes whose votes are required for an election or cluster state change. This set is automatically updated and persisted as nodes are added or removed safely.
- C It delegates the master election to an external consensus store like Consul or Etcd.
- D It requires a manual API call to 'Commit' a new master node after a partition is resolved.
Answer: B. Dynamic Voting Configuration: The cluster maintains a set of nodes whose votes are required for an election or cluster state change. This set is automatically updated and persisted as nodes are added or removed safely.
In the old system, a human had to update `(N/2)+1` manually. In the 7.x+ system (based on a Raft-like protocol), the cluster knows its own quorum requirements. If you remove nodes properly, the cluster shrinks the voting set to ensure it can still progress without a manual config change.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What are the two primary reasons for configuring one or more 'Replica Shards' for an index?
- When a String field is mapped as `text`, what process is performed to enable full-text search capability?
- What is the primary benefit of splitting an Elasticsearch index into multiple 'Primary Shards'?
- Every document stored in an Elasticsearch index is uniquely tracked by which mandatory metadata field?
- Elasticsearch search results include a metadata field called `_score`. What does this value primarily indicate?
- What is the primary architectural purpose of Elasticsearch in a modern software stack?