# Not able to create ILM for Zipkin indeces in Elasticsearch

**URL:** <https://discuss.elastic.co/t/not-able-to-create-ilm-for-zipkin-indeces-in-elasticsearch/279746>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring, docker, ilm-index-lifecycle-management\
**Created:** [July 27, 2021, 3:11pm UTC](https://discuss.elastic.co/t/not-able-to-create-ilm-for-zipkin-indeces-in-elasticsearch/279746 "2021-07-27T15:11:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SreekanthOM](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@SreekanthOM](https://discuss.elastic.co/u/SreekanthOM)\
**Post date:** [July 27, 2021, 3:11pm UTC](https://discuss.elastic.co/t/not-able-to-create-ilm-for-zipkin-indeces-in-elasticsearch/279746/1 "2021-07-27T15:11:34Z")

</div>

Zipkin is deployed in K8s and traces are working and index "zipkin-span-2021-07-27" created in ES, creating ILM has issue with without alias throwing error from zipkin pod "Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [traceId] in order to load field data by uninverting the inverted index. Note that this can use significant memory"

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 24, 2021, 3:11pm UTC](https://discuss.elastic.co/t/not-able-to-create-ilm-for-zipkin-indeces-in-elasticsearch/279746/2 "2021-08-24T15:11:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.