# Migrating from shared to local gateway **URL:** \ **Category:** Elasticsearch\ **Created:** [December 3, 2013, 2:01pm UTC](https://discuss.elastic.co/t/migrating-from-shared-to-local-gateway/14679 "2013-12-03T14:01:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![realestate](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@realestate](https://discuss.elastic.co/u/realestate)\ **Post date:** [December 3, 2013, 2:01pm UTC](https://discuss.elastic.co/t/migrating-from-shared-to-local-gateway/14679/1 "2013-12-03T14:01:54Z")
Hi A couple of questions as we are following the advice to move away from the shared gateway (in our case S3) and start using the Local Gateway with EBS volumes instead: 1. can the gateway configuration be changed one node at a time, or is a full cluster restart needed? 2. In the case an instance inherits an orphan EBS volume with old data I am assuming ElasticSearch would just ignore the local data and copy the shards from existing nodes in the cluster without any conflicts or risks for the data? 3. upgrading from 0.19.4 to 0.90 I understand a full cluster restart is needed (stop all nodes, update ElasticSearch files, start nodes) would the cluster be able to recover the data from the EBS volumes or is a full re-index required? thanks in advance John -- 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/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [December 3, 2013, 5:53pm UTC](https://discuss.elastic.co/t/migrating-from-shared-to-local-gateway/14679/2 "2013-12-03T17:53:02Z")
I can't comment on the AWS side, but you shouldn't need to do a reindex for the upgrade. ES will change whatever it needs to to the index structure on start to make it compatible. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 4 December 2013 01:01, John Lefteris [acpblmail-facebook@yahoo.com](mailto:acpblmail-facebook@yahoo.com)wrote: > Hi > > A couple of questions as we are following the advice to move away from the > shared gateway (in our case S3) and start using the Local Gateway with EBS > volumes instead: > > 1. can the gateway configuration be changed one node at a time, or is a > full cluster restart needed? > > 2. In the case an instance inherits an orphan EBS volume with old data I > am assuming Elasticsearch would just ignore the local data and copy the > shards from existing nodes in the cluster without any conflicts or risks > for the data? > > 3. upgrading from 0.19.4 to 0.90 I understand a full cluster restart is > needed (stop all nodes, update Elasticsearch files, start nodes) > would the cluster be able to recover the data from the EBS volumes or is a > full re-index required? > thanks in advance > > John > > -- > 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/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAEM624aMrU2soJ9uWuKT6S1mzbn%2B8QhM7mMMK\_ViP4jvSjRjnw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aMrU2soJ9uWuKT6S1mzbn%2B8QhM7mMMK_ViP4jvSjRjnw%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![realestate](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@realestate](https://discuss.elastic.co/u/realestate)\ **Post date:** [December 8, 2013, 2:05am UTC](https://discuss.elastic.co/t/migrating-from-shared-to-local-gateway/14679/3 "2013-12-08T02:05:58Z")
Thanks for your answer! That helps. Can anyone comment on whether the gateway settings are cluster-wide or if I could stop-\>change-gateway-config-\>start for each node in the cluster one by one with no downtime? thanks! On Tuesday, December 3, 2013 5:53:02 PM UTC, Mark Walkom wrote: > I can't comment on the AWS side, but you shouldn't need to do a reindex > for the upgrade. ES will change whatever it needs to to the index structure > on start to make it compatible. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 4 December 2013 01:01, John Lefteris \<[acpblmail...@yahoo.com](mailto:acpblmail...@yahoo.com)\ > > > wrote: > > > Hi > > > > A couple of questions as we are following the advice to move away from > > the shared gateway (in our case S3) and start using the Local Gateway with > > EBS volumes instead: > > > > 1. can the gateway configuration be changed one node at a time, or is a > > full cluster restart needed? > > > > 2. In the case an instance inherits an orphan EBS volume with old data I > > am assuming Elasticsearch would just ignore the local data and copy the > > shards from existing nodes in the cluster without any conflicts or risks > > for the data? > > > > 3. upgrading from 0.19.4 to 0.90 I understand a full cluster restart is > > needed (stop all nodes, update Elasticsearch files, start nodes) > > would the cluster be able to recover the data from the EBS volumes or is > > a full re-index required? > > thanks in advance > > > > John > > > > -- > > 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/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c4acbd2-ffdb-455f-bc00-8cf67637d15e%40googlegroups.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/88a3a823-b137-45bf-8f3a-4c8a9d1b31d1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/88a3a823-b137-45bf-8f3a-4c8a9d1b31d1%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:02am UTC](https://discuss.elastic.co/t/migrating-from-shared-to-local-gateway/14679/4 "2017-07-06T02:02:41Z")