# Upgrade from ES 1.2.x to ES 1.4 or 1.3? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 7, 2015, 5:41pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525 "2015-01-07T17:41:06Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 5:41pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/1 "2015-01-07T17:41:06Z")
I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever is the most latest (stable) in 1.3 series - so should I go for 1.4 or should stay with 1.3? the reason why I am not thinking about absolute upgrade to 1.4 is just so that if certain things like shards allocations to different node/s suddenly doesnt work or may be I am wrong too - I mean this type of sudden and obvious things just stops working - I am still new to ES world and not knowing ES fully. Not sure - need opinions on your experience if any? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 7, 2015, 5:46pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/2 "2015-01-07T17:46:32Z")
It’s most likely because on your dev system, you are running out of disk space. Elasticsearch 1.4.x does not allocate replicas if you have more than 85% disk usage. You can change this settings by modifying for example elasticsearch.yml and set: cluster.routing.allocation.disk.watermark.low: 1gb cluster.routing.allocation.disk.watermark.high: 500mb Regarding your question, I would go for 1.4. HTH -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) a écrit : > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever is the most latest (stable) in 1.3 series - so should I go for 1.4 or should stay with 1.3? > the reason why I am not thinking about absolute upgrade to 1.4 is just so that if certain things like shards allocations to different node/s suddenly doesnt work or may be I am wrong too - I mean this type of sudden and obvious things just stops working - I am still new to ES world and not knowing ES fully. > > Not sure - need opinions on your experience if any? > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout) [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/EF2BE3FD-8009-4C5C-ACC1-D4FBA1180FC3%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/EF2BE3FD-8009-4C5C-ACC1-D4FBA1180FC3%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 5:50pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/3 "2015-01-07T17:50:47Z")
Alright cool David! if this is the pain point then I dont think that I should limit this upgrade to only 1.3 - I will go for 1.4 one more thing - I already have around 300 GB(max capacity 2TB) of indexed data available in my additional storage which I exclusively kept for ES - so far this 300 gigs of data has been generated by ES1.2 - now if I move to ES 1.4 - will that cause any issue? Do I need to regenerate anything over here or ES 1.4 will automatically accept whatever has been generated by ES1.2? its more of back compatibility point which I am trying to raise here. On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > It’s most likely because on your dev system, you are running out of disk > space. > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > disk usage. > You can change this settings by modifying for example elasticsearch.yml > and set: > > cluster.routing.allocation.disk.watermark.low: 1gb > cluster.routing.allocation.disk.watermark.high: 500mb > > Regarding your question, I would go for 1.4. > > HTH > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > [http://Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) \\> > a écrit : > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > should stay with 1.3? > the reason why I am not thinking about absolute upgrade to 1.4 is just so > that if certain things like shards allocations to different node/s suddenly > doesnt work or may be I am wrong too - I mean this type of sudden and > obvious things just stops working - I am still new to ES world and not > knowing ES fully. > > Not sure - need opinions on your experience if any? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 7, 2015, 5:57pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/4 "2015-01-07T17:57:27Z")
No you don’t have to reindex. Elasticsearch can read segments generated with previous elasticsearch version. -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) a écrit : > > Alright cool David! if this is the pain point then I dont think that I should limit this upgrade to only 1.3 - I will go for 1.4 > > one more thing - I already have around 300 GB(max capacity 2TB) of indexed data available in my additional storage which I exclusively kept for ES - so far this 300 gigs of data has been generated by ES1.2 - now if I move to ES 1.4 - will that cause any issue? > Do I need to regenerate anything over here or ES 1.4 will automatically accept whatever has been generated by ES1.2? > > its more of back compatibility point which I am trying to raise here. > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > It’s most likely because on your dev system, you are running out of disk space. > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% disk usage. > You can change this settings by modifying for example elasticsearch.yml and set: > > cluster.routing.allocation.disk.watermark.low: 1gb > cluster.routing.allocation.disk.watermark.high: 500mb > > Regarding your question, I would go for 1.4. > > HTH > > -- > David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) [http://elasticsearch.com/](http://elasticsearch.com/) > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri \[gmail.com](http://gmail.com) [http://gmail.com/](http://gmail.com/)\> a écrit : > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever is the most latest (stable) in 1.3 series - so should I go for 1.4 or should stay with 1.3? > > the reason why I am not thinking about absolute upgrade to 1.4 is just so that if certain things like shards allocations to different node/s suddenly doesnt work or may be I am wrong too - I mean this type of sudden and obvious things just stops working - I am still new to ES world and not knowing ES fully. > > > > Not sure - need opinions on your experience if any? > > > > -- > > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@ \<\>[googlegroups.com](http://googlegroups.com) [http://googlegroups.com/](http://googlegroups.com/). > > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer). > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout) [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com) [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout) [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2E983BA8-1708-4AD1-8CE5-2AB2A8B15C98%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/2E983BA8-1708-4AD1-8CE5-2AB2A8B15C98%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 5:59pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/5 "2015-01-07T17:59:50Z")
Wonderful - Thanks David! On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > No you don’t have to reindex. > Elasticsearch can read segments generated with previous elasticsearch > version. > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > [http://Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) \\> > a écrit : > > Alright cool David! if this is the pain point then I dont think that I > should limit this upgrade to only 1.3 - I will go for 1.4 > > one more thing - I already have around 300 GB(max capacity 2TB) of indexed > data available in my additional storage which I exclusively kept for ES - > so far this 300 gigs of data has been generated by ES1.2 - now if I move to > ES 1.4 - will that cause any issue? > Do I need to regenerate anything over here or ES 1.4 will automatically > accept whatever has been generated by ES1.2? > > its more of back compatibility point which I am trying to raise here. > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > It’s most likely because on your dev system, you are running out of disk > > space. > > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > > disk usage. > > You can change this settings by modifying for example elasticsearch.yml > > and set: > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > Regarding your question, I would go for 1.4. > > > > HTH > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > > should stay with 1.3? > > the reason why I am not thinking about absolute upgrade to 1.4 is just so > > that if certain things like shards allocations to different node/s suddenly > > doesnt work or may be I am wrong too - I mean this type of sudden and > > obvious things just stops working - I am still new to ES world and not > > knowing ES fully. > > > > Not sure - need opinions on your experience if any? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7cacc091-cbb2-4023-b4df-0f0cead00486%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7cacc091-cbb2-4023-b4df-0f0cead00486%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 6:55pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/6 "2015-01-07T18:55:48Z")
Also one more question - lets say intially I have one node architecture - i.e. everything on one single node and additional mount is having all the ES data (index, documents etc) which is like of 300 gigs - now lets say if I add more data nodes - so going forward it will distribute the shards to different nodes or existing data will automatically be redistributed too? On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > No you don’t have to reindex. > Elasticsearch can read segments generated with previous elasticsearch > version. > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > [http://Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) \\> > a écrit : > > Alright cool David! if this is the pain point then I dont think that I > should limit this upgrade to only 1.3 - I will go for 1.4 > > one more thing - I already have around 300 GB(max capacity 2TB) of indexed > data available in my additional storage which I exclusively kept for ES - > so far this 300 gigs of data has been generated by ES1.2 - now if I move to > ES 1.4 - will that cause any issue? > Do I need to regenerate anything over here or ES 1.4 will automatically > accept whatever has been generated by ES1.2? > > its more of back compatibility point which I am trying to raise here. > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > It’s most likely because on your dev system, you are running out of disk > > space. > > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > > disk usage. > > You can change this settings by modifying for example elasticsearch.yml > > and set: > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > Regarding your question, I would go for 1.4. > > > > HTH > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > > should stay with 1.3? > > the reason why I am not thinking about absolute upgrade to 1.4 is just so > > that if certain things like shards allocations to different node/s suddenly > > doesnt work or may be I am wrong too - I mean this type of sudden and > > obvious things just stops working - I am still new to ES world and not > > knowing ES fully. > > > > Not sure - need opinions on your experience if any? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 7, 2015, 7:46pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/7 "2015-01-07T19:46:25Z")
Yes it auto distributes existing, and new, shards. On 8 January 2015 at 05:55, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > Also one more question - lets say intially I have one node architecture - > i.e. everything on one single node and additional mount is having all the > ES data (index, documents etc) which is like of 300 gigs - now lets say if > I add more data nodes - so going forward it will distribute the shards to > different nodes or existing data will automatically be redistributed too? > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > No you don’t have to reindex. > > Elasticsearch can read segments generated with previous elasticsearch > > version. > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > Alright cool David! if this is the pain point then I dont think that I > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > indexed data available in my additional storage which I exclusively kept > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > I move to ES 1.4 - will that cause any issue? > > Do I need to regenerate anything over here or ES 1.4 will automatically > > accept whatever has been generated by ES1.2? > > > > its more of back compatibility point which I am trying to raise here. > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > It’s most likely because on your dev system, you are running out of disk > > > space. > > > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > > > disk usage. > > > You can change this settings by modifying for example elasticsearch.yml > > > and set: > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > Regarding your question, I would go for 1.4. > > > > > > HTH > > > > > > -- > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > > > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > > > should stay with 1.3? > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > so that if certain things like shards allocations to different node/s > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > and obvious things just stops working - I am still new to ES world and not > > > knowing ES fully. > > > > > > Not sure - need opinions on your experience if any? > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c- > > > adcb35a51fdf%[40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f- > > 187c89f097dc%[40googlegroups.com](http://40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X\_BP7Xxr-nSdW%3D3UUfCDi3Hbg-pOujx\_f\_8gkxJ2gp%3DdA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_BP7Xxr-nSdW%3D3UUfCDi3Hbg-pOujx_f_8gkxJ2gp%3DdA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 8:10pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/8 "2015-01-07T20:10:45Z")
Oh nice - so some indexes which I have created month ago which has - lets say 5 shards on one node - after adding node - 2 of these existing shards might move to newly added data node - this is great! So when you create master, client, data node - out of these which one needs to be superly powerful in terms of RAM/CPU/SPACE - I agree that data nodes need to have superior space since they will actually store the index data but not sure which one should be powerful interms of RAM/CPU or all of them should be equally good like 12 CPU, 64 gigs of ram etc? I agree it purely depends on whats the volume of data etc but in general who should be most powerful in terms of hardware capacity? On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > Yes it auto distributes existing, and new, shards. > > On 8 January 2015 at 05:55, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Also one more question - lets say intially I have one node architecture - > > i.e. everything on one single node and additional mount is having all the > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > I add more data nodes - so going forward it will distribute the shards to > > different nodes or existing data will automatically be redistributed too? > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > No you don’t have to reindex. > > > Elasticsearch can read segments generated with previous elasticsearch > > > version. > > > > > > -- > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > indexed data available in my additional storage which I exclusively kept > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > I move to ES 1.4 - will that cause any issue? > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > accept whatever has been generated by ES1.2? > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > It’s most likely because on your dev system, you are running out of > > > > disk space. > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > 85% disk usage. > > > > You can change this settings by modifying for example elasticsearch.yml > > > > and set: > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > HTH > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > 1.4 or should stay with 1.3? > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > so that if certain things like shards allocations to different node/s > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > and obvious things just stops working - I am still new to ES world and not > > > > knowing ES fully. > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > > com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c- > > > > adcb35a51fdf%[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f- > > > 187c89f097dc%[40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 7, 2015, 9:09pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/9 "2015-01-07T21:09:21Z")
Generally - Data needs RAM, disk and CPU, client would need CPU and RAM, master can be super light (4-8GB, a single core). On 8 January 2015 at 07:10, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > Oh nice - so some indexes which I have created month ago which has - lets > say 5 shards on one node - after adding node - 2 of these existing shards > might move to newly added data node - this is great! > > So when you create master, client, data node - out of these which one > needs to be superly powerful in terms of RAM/CPU/SPACE - I agree that data > nodes need to have superior space since they will actually store the index > data but not sure which one should be powerful interms of RAM/CPU or all of > them should be equally good like 12 CPU, 64 gigs of ram etc? > > I agree it purely depends on whats the volume of data etc but in general > who should be most powerful in terms of hardware capacity? > > On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > > > Yes it auto distributes existing, and new, shards. > > > > On 8 January 2015 at 05:55, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) wrote: > > > > > Also one more question - lets say intially I have one node architecture > > > > > > - i.e. everything on one single node and additional mount is having all the > > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > > I add more data nodes - so going forward it will distribute the shards to > > > different nodes or existing data will automatically be redistributed too? > > > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > > > No you don’t have to reindex. > > > > Elasticsearch can read segments generated with previous elasticsearch > > > > version. > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > > indexed data available in my additional storage which I exclusively kept > > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > > I move to ES 1.4 - will that cause any issue? > > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > > accept whatever has been generated by ES1.2? > > > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > > > It’s most likely because on your dev system, you are running out of > > > > > disk space. > > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > > 85% disk usage. > > > > > You can change this settings by modifying for example > > > > > elasticsearch.yml and set: > > > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > > > HTH > > > > > > > > > > -- > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > > 1.4 or should stay with 1.3? > > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > > so that if certain things like shards allocations to different node/s > > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > > and obvious things just stops working - I am still new to ES world and not > > > > > knowing ES fully. > > > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > m/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > m/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zBtQJ0OGzTOrZJvQOPwHGYQzF5K2sEGBUN3eebPmrA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zBtQJ0OGzTOrZJvQOPwHGYQzF5K2sEGBUN3eebPmrA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 9:16pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/10 "2015-01-07T21:16:29Z")
I thought something similar but wasn't sure - but this answers it. On Wednesday, January 7, 2015 1:09:50 PM UTC-8, Mark Walkom wrote: > Generally - Data needs RAM, disk and CPU, client would need CPU and RAM, > master can be super light (4-8GB, a single core). > > On 8 January 2015 at 07:10, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Oh nice - so some indexes which I have created month ago which has - lets > > say 5 shards on one node - after adding node - 2 of these existing shards > > might move to newly added data node - this is great! > > > > So when you create master, client, data node - out of these which one > > needs to be superly powerful in terms of RAM/CPU/SPACE - I agree that data > > nodes need to have superior space since they will actually store the index > > data but not sure which one should be powerful interms of RAM/CPU or all of > > them should be equally good like 12 CPU, 64 gigs of ram etc? > > > > I agree it purely depends on whats the volume of data etc but in general > > who should be most powerful in terms of hardware capacity? > > > > On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > > > > > Yes it auto distributes existing, and new, shards. > > > > > > On 8 January 2015 at 05:55, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) wrote: > > > > > > > Also one more question - lets say intially I have one node architecture > > > > > > > > - i.e. everything on one single node and additional mount is having all the > > > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > > > I add more data nodes - so going forward it will distribute the shards to > > > > different nodes or existing data will automatically be redistributed too? > > > > > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > > > > > No you don’t have to reindex. > > > > > Elasticsearch can read segments generated with previous elasticsearch > > > > > version. > > > > > > > > > > -- > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > > > indexed data available in my additional storage which I exclusively kept > > > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > > > I move to ES 1.4 - will that cause any issue? > > > > > Do I need to regenerate anything over here or ES 1.4 will > > > > > automatically accept whatever has been generated by ES1.2? > > > > > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > > > > > It’s most likely because on your dev system, you are running out of > > > > > > disk space. > > > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > > > 85% disk usage. > > > > > > You can change this settings by modifying for example > > > > > > elasticsearch.yml and set: > > > > > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > > > > > HTH > > > > > > > > > > > > -- > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > > > 1.4 or should stay with 1.3? > > > > > > the reason why I am not thinking about absolute upgrade to 1.4 is > > > > > > just so that if certain things like shards allocations to different node/s > > > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > > > and obvious things just stops working - I am still new to ES world and not > > > > > > knowing ES fully. > > > > > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > > Groups "elasticsearch" group. > > > > > > To unsubscribe from this group and stop receiving emails from it, > > > > > > send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > > m/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf > > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > m/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05% > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9b6ea2b8-4f18-4516-9178-d9b9fc428e92%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/187fd43e-8459-4bfd-be73-1300afc60d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/187fd43e-8459-4bfd-be73-1300afc60d23%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 9:37pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/11 "2015-01-07T21:37:22Z")
what happens when you take off one of the node which is already having some shards allocated to it? Is it like replica would then come into play at that time? If permanently I want to decommission a node - is that a possible or that is something one shouldn't be doing? On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > Yes it auto distributes existing, and new, shards. > > On 8 January 2015 at 05:55, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Also one more question - lets say intially I have one node architecture - > > i.e. everything on one single node and additional mount is having all the > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > I add more data nodes - so going forward it will distribute the shards to > > different nodes or existing data will automatically be redistributed too? > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > No you don’t have to reindex. > > > Elasticsearch can read segments generated with previous elasticsearch > > > version. > > > > > > -- > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > indexed data available in my additional storage which I exclusively kept > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > I move to ES 1.4 - will that cause any issue? > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > accept whatever has been generated by ES1.2? > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > It’s most likely because on your dev system, you are running out of > > > > disk space. > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > 85% disk usage. > > > > You can change this settings by modifying for example elasticsearch.yml > > > > and set: > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > HTH > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > 1.4 or should stay with 1.3? > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > so that if certain things like shards allocations to different node/s > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > and obvious things just stops working - I am still new to ES world and not > > > > knowing ES fully. > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > > com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c- > > > > adcb35a51fdf%[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f- > > > 187c89f097dc%[40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 7, 2015, 10:34pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/12 "2015-01-07T22:34:18Z")
If you remove a node then the corresponding replicas around the cluster will be promoted to primaries and new replicas are initialised. You can definitely remove a node, you can either stop the service and let things recover, or use the shutdown API call to do it in a more ordered fashion. On 8 January 2015 at 08:37, Bhumir Jhaveri [bhumir81@gmail.com](mailto:bhumir81@gmail.com) wrote: > what happens when you take off one of the node which is already having > some shards allocated to it? > Is it like replica would then come into play at that time? > If permanently I want to decommission a node - is that a possible or that > is something one shouldn't be doing? > > On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > > > Yes it auto distributes existing, and new, shards. > > > > On 8 January 2015 at 05:55, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) wrote: > > > > > Also one more question - lets say intially I have one node architecture > > > > > > - i.e. everything on one single node and additional mount is having all the > > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > > I add more data nodes - so going forward it will distribute the shards to > > > different nodes or existing data will automatically be redistributed too? > > > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > > > No you don’t have to reindex. > > > > Elasticsearch can read segments generated with previous elasticsearch > > > > version. > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > > indexed data available in my additional storage which I exclusively kept > > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > > I move to ES 1.4 - will that cause any issue? > > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > > accept whatever has been generated by ES1.2? > > > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > > > It’s most likely because on your dev system, you are running out of > > > > > disk space. > > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > > 85% disk usage. > > > > > You can change this settings by modifying for example > > > > > elasticsearch.yml and set: > > > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > > > HTH > > > > > > > > > > -- > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > > 1.4 or should stay with 1.3? > > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > > so that if certain things like shards allocations to different node/s > > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > > and obvious things just stops working - I am still new to ES world and not > > > > > knowing ES fully. > > > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > m/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > m/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8zQaEBCNW0X\_3zjyZGDx8Z84p0SfG-pKbOm2jf2jhshw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8zQaEBCNW0X_3zjyZGDx8Z84p0SfG-pKbOm2jf2jhshw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 7, 2015, 10:37pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/13 "2015-01-07T22:37:00Z")
This is wonderful! thanks for the deep insights. On Wednesday, January 7, 2015 2:34:48 PM UTC-8, Mark Walkom wrote: > If you remove a node then the corresponding replicas around the cluster > will be promoted to primaries and new replicas are initialised. > You can definitely remove a node, you can either stop the service and let > things recover, or use the shutdown API call to do it in a more ordered > fashion. > > On 8 January 2015 at 08:37, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > what happens when you take off one of the node which is already having > > some shards allocated to it? > > Is it like replica would then come into play at that time? > > If permanently I want to decommission a node - is that a possible or that > > is something one shouldn't be doing? > > > > On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > > > > > Yes it auto distributes existing, and new, shards. > > > > > > On 8 January 2015 at 05:55, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) wrote: > > > > > > > Also one more question - lets say intially I have one node architecture > > > > > > > > - i.e. everything on one single node and additional mount is having all the > > > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > > > I add more data nodes - so going forward it will distribute the shards to > > > > different nodes or existing data will automatically be redistributed too? > > > > > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > > > > > No you don’t have to reindex. > > > > > Elasticsearch can read segments generated with previous elasticsearch > > > > > version. > > > > > > > > > > -- > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > > > indexed data available in my additional storage which I exclusively kept > > > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > > > I move to ES 1.4 - will that cause any issue? > > > > > Do I need to regenerate anything over here or ES 1.4 will > > > > > automatically accept whatever has been generated by ES1.2? > > > > > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > > > > > It’s most likely because on your dev system, you are running out of > > > > > > disk space. > > > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > > > 85% disk usage. > > > > > > You can change this settings by modifying for example > > > > > > elasticsearch.yml and set: > > > > > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > > > > > HTH > > > > > > > > > > > > -- > > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > > > 1.4 or should stay with 1.3? > > > > > > the reason why I am not thinking about absolute upgrade to 1.4 is > > > > > > just so that if certain things like shards allocations to different node/s > > > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > > > and obvious things just stops working - I am still new to ES world and not > > > > > > knowing ES fully. > > > > > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > > Groups "elasticsearch" group. > > > > > > To unsubscribe from this group and stop receiving emails from it, > > > > > > send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > > m/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf > > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.co](https://groups.google.co) > > > > > m/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc > > > > > %[40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05% > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/33d1e12d-e527-495b-854e-e59987a649ae%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d266b7db-72b3-4573-9f4a-01d17a3885bc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d266b7db-72b3-4573-9f4a-01d17a3885bc%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ankit\_Jain\_2](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Ankit\_Jain\_2](https://discuss.elastic.co/u/Ankit_Jain_2)\ **Post date:** [January 7, 2015, 10:50pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/14 "2015-01-07T22:50:57Z")
Quick question: Does ES support clusters with mixed versions (to do a rolling restart during an upgrade)? Is there a known process for upgrading a cluster? Thank you! Ankit On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > It’s most likely because on your dev system, you are running out of disk > space. > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > disk usage. > You can change this settings by modifying for example elasticsearch.yml > and set: > > cluster.routing.allocation.disk.watermark.low: 1gb > cluster.routing.allocation.disk.watermark.high: 500mb > > Regarding your question, I would go for 1.4. > > HTH > > -- > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > [http://Elasticsearch.com](http://Elasticsearch.com)_ > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) \\> > a écrit : > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > should stay with 1.3? > the reason why I am not thinking about absolute upgrade to 1.4 is just so > that if certain things like shards allocations to different node/s suddenly > doesnt work or may be I am wrong too - I mean this type of sudden and > obvious things just stops working - I am still new to ES world and not > knowing ES fully. > > Not sure - need opinions on your experience if any? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 7, 2015, 11:52pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/15 "2015-01-07T23:52:36Z")
Yes and yes - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. On 8 January 2015 at 09:50, Ankit Jain [ankit@quettra.com](mailto:ankit@quettra.com) wrote: > Quick question: Does ES support clusters with mixed versions (to do a > rolling restart during an upgrade)? Is there a known process for upgrading > a cluster? > > Thank you! > > Ankit > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > It’s most likely because on your dev system, you are running out of disk > > space. > > Elasticsearch 1.4.x does not allocate replicas if you have more than 85% > > disk usage. > > You can change this settings by modifying for example elasticsearch.yml > > and set: > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > Regarding your question, I would go for 1.4. > > > > HTH > > > > -- > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or whichever > > is the most latest (stable) in 1.3 series - so should I go for 1.4 or > > should stay with 1.3? > > the reason why I am not thinking about absolute upgrade to 1.4 is just so > > that if certain things like shards allocations to different node/s suddenly > > doesnt work or may be I am wrong too - I mean this type of sudden and > > obvious things just stops working - I am still new to ES world and not > > knowing ES fully. > > > > Not sure - need opinions on your experience if any? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf% > > [40googlegroups.com](http://40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/212b4ef1-9310-43ee-b312-9f7db8499a5a%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8V4qqkQQgyLeiwhxJT2AW2RFHH7yX4oVE-RyChZF%2BM\_Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8V4qqkQQgyLeiwhxJT2AW2RFHH7yX4oVE-RyChZF%2BM_Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 8, 2015, 12:29am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/16 "2015-01-08T00:29:58Z")
Here is what I did - I had some data - I bumped up the ES version and then restarted the ES - It started giving following warnings - [2015-01-07 16:26:43,881][WARN][cluster.action.shard] [my\_node] [data][3] received shard failed for [data][3], node[WIUD-O9XRiyg3Rk5RxHhZw], [P], s[INITIALIZING], indexUUID [781tTXk2Qe6GwwHgXKx2pw], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[data][3] failed to recover shard]; nested: IllegalArgumentException[No type mapped for [8]]; ]] [2015-01-07 16:26:43,887][WARN][cluster.action.shard] [my\_node] [data][1] sending failed shard for [data][1], node[WIUD-O9XRiyg3Rk5RxHhZw], [P], s[INITIALIZING], indexUUID [781tTXk2Qe6GwwHgXKx2pw], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[data][1] failed to recover shard]; nested: IllegalArgumentException[No type mapped for [8]]; ]] [2015-01-07 16:26:43,967][WARN][indices.cluster] [my\_node] [data][4] failed to start shard org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: [data][4] failed to recover shard at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:241) at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:132) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) Its still doing some processing which I could figured out from kopf monitoring - but not sure how long it would take and whether I have screwed up the upgrade here? On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > Yes it auto distributes existing, and new, shards. > > On 8 January 2015 at 05:55, Bhumir Jhaveri \<[bhum...@gmail.com](mailto:bhum...@gmail.com) > \\> wrote: > > > Also one more question - lets say intially I have one node architecture - > > i.e. everything on one single node and additional mount is having all the > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > I add more data nodes - so going forward it will distribute the shards to > > different nodes or existing data will automatically be redistributed too? > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > No you don’t have to reindex. > > > Elasticsearch can read segments generated with previous elasticsearch > > > version. > > > > > > -- > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > indexed data available in my additional storage which I exclusively kept > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > I move to ES 1.4 - will that cause any issue? > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > accept whatever has been generated by ES1.2? > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > It’s most likely because on your dev system, you are running out of > > > > disk space. > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > 85% disk usage. > > > > You can change this settings by modifying for example elasticsearch.yml > > > > and set: > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > HTH > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > 1.4 or should stay with 1.3? > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > so that if certain things like shards allocations to different node/s > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > and obvious things just stops working - I am still new to ES world and not > > > > knowing ES fully. > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > > com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c- > > > > adcb35a51fdf%[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f- > > > 187c89f097dc%[40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8f061b48-96f7-447b-857a-ed4368bbfd3a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8f061b48-96f7-447b-857a-ed4368bbfd3a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Bhumir\_Jhaveri](https://avatars.discourse-cdn.com/v4/letter/b/9d8465/32.png) [@Bhumir\_Jhaveri](https://discuss.elastic.co/u/Bhumir_Jhaveri)\ **Post date:** [January 8, 2015, 6:27pm UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/17 "2015-01-08T18:27:27Z")
Did anyone noticed this? On Wednesday, January 7, 2015 4:29:58 PM UTC-8, Bhumir Jhaveri wrote: > Here is what I did - > I had some data - I bumped up the ES version and then restarted the ES - > > It started giving following warnings - > > [2015-01-07 16:26:43,881][WARN][cluster.action.shard] [my\_node] > [data][3] received shard failed for [data][3], > node[WIUD-O9XRiyg3Rk5RxHhZw], [P], s[INITIALIZING], indexUUID > [781tTXk2Qe6GwwHgXKx2pw], reason [Failed to start shard, message > [IndexShardGatewayRecoveryException[[data][3] failed to recover shard]; > nested: IllegalArgumentException[No type mapped for [8]]; ]] > [2015-01-07 16:26:43,887][WARN][cluster.action.shard] [my\_node] > [data][1] sending failed shard for [data][1], node[WIUD-O9XRiyg3Rk5RxHhZw], > [P], s[INITIALIZING], indexUUID [781tTXk2Qe6GwwHgXKx2pw], reason [Failed to > start shard, message [IndexShardGatewayRecoveryException[[data][1] failed > to recover shard]; nested: IllegalArgumentException[No type mapped for > [8]]; ]] > [2015-01-07 16:26:43,967][WARN][indices.cluster] [my\_node] > [data][4] failed to start shard > org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: > [data][4] failed to recover shard > at > org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:241) > at > org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:132) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > > Its still doing some processing which I could figured out from kopf > monitoring - but not sure how long it would take and whether I have screwed > up the upgrade here? > > On Wednesday, January 7, 2015 11:46:57 AM UTC-8, Mark Walkom wrote: > > > Yes it auto distributes existing, and new, shards. > > > > On 8 January 2015 at 05:55, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) wrote: > > > > > Also one more question - lets say intially I have one node architecture > > > > > > - i.e. everything on one single node and additional mount is having all the > > > ES data (index, documents etc) which is like of 300 gigs - now lets say if > > > I add more data nodes - so going forward it will distribute the shards to > > > different nodes or existing data will automatically be redistributed too? > > > > > > On Wednesday, January 7, 2015 9:57:44 AM UTC-8, David Pilato wrote: > > > > > > > No you don’t have to reindex. > > > > Elasticsearch can read segments generated with previous elasticsearch > > > > version. > > > > > > > > -- > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > [http://Elasticsearch.com](http://Elasticsearch.com)_ > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > Le 7 janv. 2015 à 18:50, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > Alright cool David! if this is the pain point then I dont think that I > > > > should limit this upgrade to only 1.3 - I will go for 1.4 > > > > > > > > one more thing - I already have around 300 GB(max capacity 2TB) of > > > > indexed data available in my additional storage which I exclusively kept > > > > for ES - so far this 300 gigs of data has been generated by ES1.2 - now if > > > > I move to ES 1.4 - will that cause any issue? > > > > Do I need to regenerate anything over here or ES 1.4 will automatically > > > > accept whatever has been generated by ES1.2? > > > > > > > > its more of back compatibility point which I am trying to raise here. > > > > > > > > On Wednesday, January 7, 2015 9:46:50 AM UTC-8, David Pilato wrote: > > > > > > > > > It’s most likely because on your dev system, you are running out of > > > > > disk space. > > > > > Elasticsearch 1.4.x does not allocate replicas if you have more than > > > > > 85% disk usage. > > > > > You can change this settings by modifying for example > > > > > elasticsearch.yml and set: > > > > > > > > > > cluster.routing.allocation.disk.watermark.low: 1gb > > > > > cluster.routing.allocation.disk.watermark.high: 500mb > > > > > > > > > > Regarding your question, I would go for 1.4. > > > > > > > > > > HTH > > > > > > > > > > -- > > > > > _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com) > > > > > [http://elasticsearch.com/](http://elasticsearch.com/)_ > > > > > @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr > > > > > [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs > > > > > [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs) > > > > > > > > > > Le 7 janv. 2015 à 18:41, Bhumir Jhaveri [bhum...@gmail.com](mailto:bhum...@gmail.com) a écrit : > > > > > > > > > > I am planning to upgrade from ES 1.2.2 to ES 1.4.2 or 1.3.9 or > > > > > whichever is the most latest (stable) in 1.3 series - so should I go for > > > > > 1.4 or should stay with 1.3? > > > > > the reason why I am not thinking about absolute upgrade to 1.4 is just > > > > > so that if certain things like shards allocations to different node/s > > > > > suddenly doesnt work or may be I am wrong too - I mean this type of sudden > > > > > and obvious things just stops working - I am still new to ES world and not > > > > > knowing ES fully. > > > > > > > > > > Not sure - need opinions on your experience if any? > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > > > com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c- > > > > > adcb35a51fdf%[40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ae8afb06-d923-4bf6-ac3c-adcb35a51fdf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google](https://groups.google). > > > > com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f- > > > > 187c89f097dc%[40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5e503a64-c9b2-42f2-9d0f-187c89f097dc%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b2818693-9307-44fc-af38-b529d2fc3d05%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e593c94f-333d-48b9-8f55-1af5770233df%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e593c94f-333d-48b9-8f55-1af5770233df%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:39am UTC](https://discuss.elastic.co/t/upgrade-from-es-1-2-x-to-es-1-4-or-1-3/21525/18 "2017-07-06T00:39:59Z")