# Kibana: Cold indices not showing when using filter in index management **URL:** \ **Category:** Kibana\ **Tags:** ilm-index-lifecycle-management\ **Created:** [January 2, 2024, 7:36am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200 "2024-01-02T07:36:50Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![basiltitus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiltitus/32/132851_2.png) [@basiltitus](https://discuss.elastic.co/u/basiltitus)\ **Post date:** [January 2, 2024, 7:36am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/1 "2024-01-02T07:36:50Z")
I have a two node cluster with a master/hot and a single data node defined in cold tier. I have created few indices for testing data tier. But when I apply " **lifecycle phase**" filter the indices supposed to be in cold tier is not listing, at the same time 'hot' are listing if I change filter value to 'hot'. If I don't use any filter all indices are listed including 'hot' and 'cold'. The reason I say they are cold tier is that If I query **GET /\_cat/shards/** using Dev tools I can see it's residing in cold node. If I click any one of the cold index I can see there is no errors and current phase showing as 'completed'. What can be the reason it's not showing in filter when select 'cold' or am I missing something? ```auto PUT _ilm/policy/hex_rollover { "policy": { "phases": { "hot": { "min_age": "0ms", "actions": { "rollover": { "max_docs": 5 }, "set_priority": { "priority": 100 } } }, "cold": { "min_age": "1h", "actions": { "allocate": { "include": {}, "exclude": {}, "require": { "node_type": "cold" } }, "set_priority": { "priority": 0 } } } } } } ``` ---
**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\ **Post date:** [January 2, 2024, 9:37am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/2 "2024-01-02T09:37:07Z")
Hi, In your case, the "min\_age" for the cold phase is set to "1h", which means the cold phase actions (like moving the index to the cold node) start 1 hour after the index enters the hot phase. However, the index is still considered to be in the hot tier until these actions are completed. If you want to see the indices in the cold tier when you apply the "lifecycle phase" filter, you might need to wait until the cold phase actions have been completed. You can check the status of these actions by looking at the ILM explain API. Regards ---
**Author:** ![basiltitus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiltitus/32/132851_2.png) [@basiltitus](https://discuss.elastic.co/u/basiltitus)\ **Post date:** [January 3, 2024, 1:29am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/3 "2024-01-03T01:29:12Z")
The indices are already in cold node which I can see using **GET /\_cat/shards/** and also these indices are created and rolled over days ago. When I apply 'hot' filter only the current write index is listed. None of other phase is listing rest of indices but when I remove filter all indices are listed. In below image db2 is my cold node. ![Screenshot 2024-01-03 at 9.27.10 AM](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a4c2f2f1166ebd07245fec8d00438d6668d341fc.png) ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [January 3, 2024, 2:40am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/4 "2024-01-03T02:40:42Z")
Can you share a screenshot of what you are seeing in Index Management? It is really not clear what is your issue, but if filter by the lifecycle phase and choose _hot_, only the index in the _hot_ phase will be shown, indices already in other lifecycle phases, like rolled over indices, will not be shown. ---
**Author:** ![basiltitus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiltitus/32/132851_2.png) [@basiltitus](https://discuss.elastic.co/u/basiltitus)\ **Post date:** [January 3, 2024, 2:57am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/5 "2024-01-03T02:57:08Z")
![Screenshot 2024-01-03 at 10.52.39 AM](https://us1.discourse-cdn.com/elastic/original/3X/9/4/94414ce699133927bc9e76bfa4a8dd5266208c4d.png) Here when I select 'cold' why indices in the cold node are not listed. If you see my my previous screenshot there you can see except '000007' write index all indices are on db2 which is my cold node. ---
**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\ **Post date:** [January 3, 2024, 9:25am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/6 "2024-01-03T09:25:09Z")
Hi, Could you execute this command: GET \_cat/nodes?v ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [January 3, 2024, 12:43pm UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/7 "2024-01-03T12:43:27Z")
Please share the `elasticsearch.yml` of both of your nodes. Also, run the request `GET /_ilm/explain` for one of your old indices and share the result. Like `GET hex-data-000001/_ilm/explain` ---
**Author:** ![basiltitus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiltitus/32/132851_2.png) [@basiltitus](https://discuss.elastic.co/u/basiltitus)\ **Post date:** [January 4, 2024, 2:53am UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/8 "2024-01-04T02:53:58Z")
**GET hex-data-000001/\_ilm/explain** gives this ```auto { "indices" : { "hex-data-000001" : { "index" : "hex-data-000001", "managed" : true, "policy" : "hex_rollover", "lifecycle_date_millis" : 1703211314319, "age" : "13.04d", "phase" : "completed", "phase_time_millis" : 1703214920429, "action" : "completed", "action_time_millis" : 1703214920429, "step" : "completed", "step_time_millis" : 1703214920429, "phase_execution" : { "policy" : "hex_rollover", "version" : 1, "modified_date_in_millis" : 1703140459345 } } } } ``` ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [January 4, 2024, 12:40pm UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/9 "2024-01-04T12:40:47Z")
You didn't share the `elasticsearch.yml` of your nodes as asked. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 1, 2024, 12:41pm UTC](https://discuss.elastic.co/t/kibana-cold-indices-not-showing-when-using-filter-in-index-management/350200/10 "2024-02-01T12:41:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.