# Rolling upgrade from 5.6.6 to 6.3.2 fails due to NaN in float field

**URL:** <https://discuss.elastic.co/t/rolling-upgrade-from-5-6-6-to-6-3-2-fails-due-to-nan-in-float-field/145926>\
**Category:** Elasticsearch\
**Created:** [August 24, 2018, 1:41pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-5-6-6-to-6-3-2-fails-due-to-nan-in-float-field/145926 "2018-08-24T13:41:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![faxm0dem](https://avatars.discourse-cdn.com/v4/letter/f/c77e96/32.png) [@faxm0dem](https://discuss.elastic.co/u/faxm0dem)\
**Post date:** [August 24, 2018, 1:41pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-5-6-6-to-6-3-2-fails-due-to-nan-in-float-field/145926/1 "2018-08-24T13:41:36Z")

</div>

Hi,  
I have NaNs in a float field. This worked in 5.6.6, but I can't upgrade to 6.y as it apparently doesn't like it.  
As soon as I try to upgrade one node, I can see this in the log:

`IllegalArgumentException[[float] supports only finite values, but got [NaN]`

The question is: do I have to reindex, or could I get away with deleting the documents having NaNs?  
Is there any other solution to a full reindex?

---

<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:** [September 21, 2018, 1:41pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-5-6-6-to-6-3-2-fails-due-to-nan-in-float-field/145926/2 "2018-09-21T13:41:44Z")

</div>

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