# Elasicsearch index error: org.elasticsearch.core.Tuple.v2()" is null

**URL:** <https://discuss.elastic.co/t/elasicsearch-index-error-org-elasticsearch-core-tuple-v2-is-null/329763>\
**Category:** Elasticsearch\
**Created:** [April 11, 2023, 4:06pm UTC](https://discuss.elastic.co/t/elasicsearch-index-error-org-elasticsearch-core-tuple-v2-is-null/329763 "2023-04-11T16:06:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vanwoes](https://avatars.discourse-cdn.com/v4/letter/v/ba8739/32.png) [@vanwoes](https://discuss.elastic.co/u/vanwoes)\
**Post date:** [April 11, 2023, 4:06pm UTC](https://discuss.elastic.co/t/elasicsearch-index-error-org-elasticsearch-core-tuple-v2-is-null/329763/1 "2023-04-11T16:06:53Z")

</div>

Hi there,

We have recently moved from a single node to multi node cluster and I have set up an ILM to move from hot, warm to cold.

I keep seeing data moving from cold to warm despite it being marked as complete. I'm confused why cold data is being moved to warm. When I go to the index, I see this error:

`Index lifecycle error

null\_pointer\_exception: Cannot invoke "org.elasticsearch.xpack.core.ilm.Step.getKey()" because the return value of "org.elasticsearch.core.Tuple.v2()" is null`

Unfortunately I can't find anything online about this. Does anyone have any advise?

Thank you.

---

<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:** [May 9, 2023, 4:07pm UTC](https://discuss.elastic.co/t/elasicsearch-index-error-org-elasticsearch-core-tuple-v2-is-null/329763/2 "2023-05-09T16:07:33Z")

</div>

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