You set number_of_shards to 1 but your data size grows to 200GB. What is the main problem with this shard sizing?

medium📝 Debug Q14 of Q15

Elasticsearch - Performance and Scaling

You set number_of_shards to 1 but your data size grows to 200GB. What is the main problem with this shard sizing?

AIndex refresh interval is too short

BToo many shards causing overhead

CReplica count is zero

DShard size is too large, causing slower search and indexing

Step-by-Step Solution

Solution:

Step 1: Analyze shard size impact
One shard holding 200GB is large and can slow down search and indexing.
Step 2: Identify correct problem
Too few shards for large data causes performance issues, not replica count or refresh interval.
Final Answer:
Shard size is too large, causing slower search and indexing -> Option D
Quick Check:
Large shard size = slower performance [OK]

Quick Trick: Avoid very large single shards [OK]

Common Mistakes:

MISTAKES

Master "Performance and Scaling" in Elasticsearch

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Elasticsearch Quizzes