# Problem With ES Upgrade(2.x to 5.x)
**URL:** https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065
**Category:** Elasticsearch
**Created:** [August 23, 2017, 11:59am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065 "2017-08-23T11:59:39Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@abhiCR7](https://discuss.elastic.co/u/abhiCR7)
#### Post date: [August 23, 2017, 11:59am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/1 "2017-08-23T11:59:39Z")
I have currently v2.4 Elasticsearch in production and in process to upgrade it to v5.5.
I'm facing problem with
index.mapping.total\_fields.limit: 1000
index.mapping.nested\_fields.limit: 50
My current total fields is in the order of 13000 and nested\_fields around 100.
Since this is non-dynamic field I'm not able to update it. Is creating new index the only option?
if no, Is there any way I can upgrade without creating new index so I can change the default values of these settings?
---
### Author:  [@jpountz](https://discuss.elastic.co/u/jpountz)
#### Post date: [August 23, 2017, 9:38pm UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/2 "2017-08-23T21:38:41Z")
I don't think this is a scenario that we planned. I'd suggest to open a Github issue.
---
### Author:  [@abhiCR7](https://discuss.elastic.co/u/abhiCR7)
#### Post date: [August 24, 2017, 6:00am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/3 "2017-08-24T06:00:01Z")
@rjernst @jpountz I had created issue for the same here [https://github.com/elastic/elasticsearch/issues/26343](https://github.com/elastic/elasticsearch/issues/26343).
Although it would be really helpful if I could one quick clarification.
So if I upgrade without changing the field limits, will that result in data loss or something else?
---
### Author:  [@jpountz](https://discuss.elastic.co/u/jpountz)
#### Post date: [August 24, 2017, 8:21am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/4 "2017-08-24T08:21:54Z")
My bad, I had misread the issue and thought that the upgrade failed for you. But actually you haven't tried out yet right?
I just tested locally and the update was successful. The reason is that those limits are only enforced for mapping updates. When upgrading to a new version, mappings are only recovered so you should not have any issues.
---
### Author:  [@abhiCR7](https://discuss.elastic.co/u/abhiCR7)
#### Post date: [August 24, 2017, 9:30am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/5 "2017-08-24T09:30:27Z")
Cool. Thanks @jpountz 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 21, 2017, 9:30am UTC](https://discuss.elastic.co/t/problem-with-es-upgrade-2-x-to-5-x/98065/6 "2017-09-21T09:30:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.