Elasticsearch - Basics and ArchitectureAn index has 5 primary shards and 1 replica. You add a new node to the cluster. What happens to the shard allocation?AThe new node becomes master automaticallyBAll shards remain on original nodes until manually movedCElasticsearch rebalances shards to distribute them evenly across all nodesDReplicas are deleted to save spaceCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand shard allocation behaviorElasticsearch automatically rebalances shards to optimize resource use when nodes change.Step 2: Analyze impact of adding a nodeAdding a node triggers shard reallocation to spread shards evenly, improving performance and fault tolerance.Final Answer:Elasticsearch rebalances shards to distribute them evenly across all nodes -> Option CQuick Check:Shard rebalancing occurs on cluster changes [OK]Quick Trick: New nodes trigger shard rebalancing [OK]Common Mistakes:MISTAKESAssuming shards stay fixed without manual actionThinking new node becomes master automaticallyBelieving replicas are deleted on node addition
Master "Basics and Architecture" in Elasticsearch9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Elasticsearch Quizzes Basic Search Queries - Match phrase query - Quiz 12easy Basic Search Queries - Range query - Quiz 12easy Basic Search Queries - Match query - Quiz 13medium Basic Search Queries - Bool query (must, should, must_not, filter) - Quiz 11easy Document Operations - Bulk API for batch operations - Quiz 8hard Document Operations - Indexing a document (POST/PUT) - Quiz 6medium Elasticsearch Basics and Architecture - First search query - Quiz 9hard Index Management - Index aliases - Quiz 1easy Mappings and Data Types - Geo-point and geo-shape types - Quiz 8hard Search Results and Scoring - Sorting results - Quiz 14medium