# ILM is not Working properly for ECK **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [July 7, 2020, 7:02pm UTC](https://discuss.elastic.co/t/ilm-is-not-working-properly-for-eck/240207 "2020-07-07T19:02:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Melvin\_Ramos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/melvin_ramos/32/46467_2.png) [@Melvin\_Ramos](https://discuss.elastic.co/u/Melvin_Ramos)\ **Post date:** [July 7, 2020, 7:02pm UTC](https://discuss.elastic.co/t/ilm-is-not-working-properly-for-eck/240207/1 "2020-07-07T19:02:56Z")
Hello all, We've been running a ECK last May, 2020 and there are some weird issues we are seeing ES 7.6.2 Context: ECK 1.1.0 Hot-Warm Architecture 4 HotNodes = 64G Ram - 5TB Storage Fast SSD 8 warm Nodes = 28G ram - 8TB Storage Local Storage 3 Master nodes - 4G ram 3G Storage 1 ingest node = 4G ram and 2G storage 3 Kibana nodes = 4G ram We are ingesting close to 1.5TB a day and for some reason the data goes to our Warm Nodes instead of Hot nodes. our index is **p44.api.log.2020.07.07** and if I look at the hot threads from the node, I can see that is being written there, and the Stack Monitoring is exactly pointing to warm Nodes, to fix it I have to force reroute to HOT. Are there anything missing on our ILM? ``` 64.3% (321.4ms out of 500ms) cpu usage by thread 'elasticsearch[prod-logs-es-warmv1-4][[p44.api.log.2020.07.07][2]: Lucene Merge Thread #1697]' 2/10 snapshots sharing following 24 elements java.base@13.0.2/jdk.internal.misc.Unsafe.park(Native Method) java.base@13.0.2/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:235) java.base@13.0.2/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123) app//org.apache.lucene.index.MergePolicy$OneMergeProgress.pauseNanos(MergePolicy.java:156) app//org.apache.lucene.index.MergeRateLimiter.maybePause(MergeRateLimiter.java:148) app//org.apache.lucene.index.MergeRateLimiter.pause(MergeRateLimiter.java:93) app//org.apache.lucene.store.RateLimitedIndexOutput.checkRate(RateLimitedIndexOutput.java:78) app//org.apache.lucene.store.RateLimitedIndexOutput.writeBytes(RateLimitedIndexOutput.java:72) app//org.apache.lucene.store.DataOutput.writeBytes(DataOutput.java:52) app//org.apache.lucene.store.RAMOutputStream.writeTo(RAMOutputStream.java:90) ``` Stack MOnitoring ![Screen Shot 2020-07-07 at 2.09.42 PM](https://us1.discourse-cdn.com/elastic/original/3X/d/6/d6d73662dbbd9d521319241085aa266ae99a2ed3.png) ILM ![Screen Shot 2020-07-07 at 2.01.19 PM](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c763391789823811ffc6331b4949de2249e240c.png) ---
**Author:** ![Melvin\_Ramos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/melvin_ramos/32/46467_2.png) [@Melvin\_Ramos](https://discuss.elastic.co/u/Melvin_Ramos)\ **Post date:** [July 10, 2020, 6:06pm UTC](https://discuss.elastic.co/t/ilm-is-not-working-properly-for-eck/240207/2 "2020-07-10T18:06:31Z")
We Solved this by adding: ```auto { "routing" : { "allocation" : { "require" : { "data" : "hot", "_id":"" } } } } ``` Effectively telling the index to start at HOT. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 7, 2020, 6:06pm UTC](https://discuss.elastic.co/t/ilm-is-not-working-properly-for-eck/240207/3 "2020-08-07T18:06:40Z")
Closed on August 7, 2020, 6:06pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.