Elasticsearch medium
In a well-configured cluster, what specifically happens when a 'Master-Eligible' node is elected as the active Master?
- A It begins processing all incoming search traffic to act as a global load balancer.
- B It takes responsibility for managing cluster-wide metadata, such as mapping definitions, shard allocation, and tracking node availability.
- C It moves all index data to its local disk to act as a centralized authority.
- D It disables the REST API on other nodes to ensure single-point-of-entry security.
Answer: B. It takes responsibility for managing cluster-wide metadata, such as mapping definitions, shard allocation, and tracking node availability.
The Master node is the 'Architect'. It ensures the cluster is healthy and consistent. It does NOT handle searching or indexing of documents; those tasks are offloaded to 'Data Nodes'. This separation of concerns prevents a heavy query from crashing the node that manages the cluster's stability.
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?