Bird
Raised Fist0

You configured an ILM policy to move indices to warm nodes after 10 days, but indices remain on hot nodes. What is a likely cause?

medium📝 Debug Q6 of Q15
Elasticsearch - Performance and Scaling
You configured an ILM policy to move indices to warm nodes after 10 days, but indices remain on hot nodes. What is a likely cause?
AILM policy is missing cold phase
BWarm nodes are not tagged with correct attribute
CHot nodes have insufficient disk space
DIndices are read-only
Step-by-Step Solution
Solution:

  1. Step 1: Check node tagging for warm nodes

    If warm nodes lack correct attribute, ILM cannot move indices there.

  2. Step 2: Identify why indices stay on hot nodes

    Incorrect or missing warm node tags prevent movement.

  3. Final Answer:

    Warm nodes are not tagged with correct attribute -> Option B

  4. Quick Check:

    Missing warm node tag = indices stay on hot [OK]
Quick Trick: Verify node attributes match ILM phases [OK]
Common Mistakes:
MISTAKES
  • Assuming missing cold phase blocks warm move
  • Thinking disk space on hot nodes causes this
  • Believing read-only indices prevent phase move

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Elasticsearch Quizzes
Cluster Management - Cross-cluster search - Quiz 1easy Cluster Management - Snapshot and restore - Quiz 15hard ELK Stack Integration - Why ELK stack provides observability - Quiz 3easy Kibana and Visualization - Discover for data exploration - Quiz 8hard Kibana and Visualization - Visualization types - Quiz 10hard Kibana and Visualization - Why Kibana visualizes Elasticsearch data - Quiz 13medium Kibana and Visualization - Kibana setup and connection - Quiz 2easy Security - Encryption in transit and at rest - Quiz 13medium Security - Field and document level security - Quiz 3easy Security - API key management - Quiz 3easy