# Value of Gateway in non-cloud environments **URL:** \ **Category:** Elasticsearch\ **Created:** [July 28, 2011, 11:03pm UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991 "2011-07-28T23:03:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 28, 2011, 11:03pm UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/1 "2011-07-28T23:03:09Z")
Hi, I've read various information about the concept of Gateway in ES and I'm wondering what value Gateway adds when one is not deploying ES in a cloud? In a cloud like AWS local storage is not necessarily persistent - when you stop an EC2 instance I believe its local data is gone. But what if you are deploying ES to a set of your own servers where this is not the case? Which type of gw should one use? local? fs? ## Thanks, Otis Sematext is hiring search engineers - [http://sematext.com/about/jobs.html](http://sematext.com/about/jobs.html) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 29, 2011, 6:19am UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/2 "2011-07-29T06:19:49Z")
local, the default, is the recommended one, and actually it is also the one being used in most cases in cloud environments as well. On Fri, Jul 29, 2011 at 2:03 AM, Otis Gospodnetic \< [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)\> wrote: > Hi, > > I've read various information about the concept of Gateway in ES and > I'm wondering what value Gateway adds when one is not deploying ES in > a cloud? In a cloud like AWS local storage is not necessarily > persistent - when you stop an EC2 instance I believe its local data is > gone. But what if you are deploying ES to a set of your own servers > where this is not the case? Which type of gw should one use? local? > fs? > > ## Thanks, Otis > > Sematext is hiring search engineers - [Jobs - Sematext](http://sematext.com/about/jobs.html) ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 29, 2011, 8:35am UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/3 "2011-07-29T08:35:27Z")
Thanks Shay. In case of "local" all index data stays local spread over N replicas and M shards. And the index settings/configs/mappings/state/etc. is all stored locally (on local disks), right? And what about replicas of this data? Is this stored in 1 central place or are there copies/replicas of index settings/configs/mappings/state/etc. on multiple cluster nodes? I couldn't find this stated in the guide or anywhere else. ## Thanks, Otis Sematext is hiring search engineers - [Jobs](http://sematext.com/about/jobs.html) On Jul 29, 2:19 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > local, the default, is the recommended one, and actually it is also the one > being used in most cases in cloud environments as well. > > On Fri, Jul 29, 2011 at 2:03 AM, Otis Gospodnetic \< > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > Hi, > > > I've read various information about the concept of Gateway in ES and > > I'm wondering what value Gateway adds when one is not deploying ES in > > a cloud? In a cloud like AWS local storage is not necessarily > > persistent - when you stop an EC2 instance I believe its local data is > > gone. But what if you are deploying ES to a set of your own servers > > where this is not the case? Which type of gw should one use? local? > > fs? > > > ## Thanks, Otis > > > > Sematext is hiring search engineers -[Jobs](http://sematext.com/about/jobs.html) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 29, 2011, 10:33am UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/4 "2011-07-29T10:33:30Z")
Thats stored on all the eligible master nodes (which in a default config, its all nodes). On Fri, Jul 29, 2011 at 11:35 AM, Otis Gospodnetic \< [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)\> wrote: > Thanks Shay. > > In case of "local" all index data stays local spread over N replicas > and M shards. > And the index settings/configs/mappings/state/etc. is all stored > locally (on local disks), right? And what about replicas of this > data? Is this stored in 1 central place or are there copies/replicas > of index settings/configs/mappings/state/etc. on multiple cluster > nodes? I couldn't find this stated in the guide or anywhere else. > > ## Thanks, Otis > > Sematext is hiring search engineers - [Jobs - Sematext](http://sematext.com/about/jobs.html) > > On Jul 29, 2:19 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > local, the default, is the recommended one, and actually it is also the > > one > > being used in most cases in cloud environments as well. > > > > On Fri, Jul 29, 2011 at 2:03 AM, Otis Gospodnetic \< > > > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > > > Hi, > > > > > I've read various information about the concept of Gateway in ES and > > > I'm wondering what value Gateway adds when one is not deploying ES in > > > a cloud? In a cloud like AWS local storage is not necessarily > > > persistent - when you stop an EC2 instance I believe its local data is > > > gone. But what if you are deploying ES to a set of your own servers > > > where this is not the case? Which type of gw should one use? local? > > > fs? > > > > > ## Thanks, Otis > > > > > > Sematext is hiring search engineers - > > > [Jobs - Sematext](http://sematext.com/about/jobs.html) ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 29, 2011, 8:10pm UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/5 "2011-07-29T20:10:56Z")
Hi, Would it then be true to say that pretty much the only (or at least the main) scenario where Shared FS gw makes more sense over the Local gw is when one is dealing with servers whose local storage is ephemeral/temporary, as is the case in EC2? ## Thanks, Otis Sematext is hiring search engineers - [Jobs](http://sematext.com/about/jobs.html) On Jul 29, 6:33 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Thats stored on all the eligible master nodes (which in a default config, > its all nodes). > > On Fri, Jul 29, 2011 at 11:35 AM, Otis Gospodnetic \< > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > Thanks Shay. > > > In case of "local" all index data stays local spread over N replicas > > and M shards. > > And the index settings/configs/mappings/state/etc. is all stored > > locally (on local disks), right? And what about replicas of this > > data? Is this stored in 1 central place or are there copies/replicas > > of index settings/configs/mappings/state/etc. on multiple cluster > > nodes? I couldn't find this stated in the guide or anywhere else. > > > ## Thanks, Otis > > > > Sematext is hiring search engineers -[Jobs](http://sematext.com/about/jobs.html) > > > On Jul 29, 2:19 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > local, the default, is the recommended one, and actually it is also the > > > one > > > being used in most cases in cloud environments as well. > > > > On Fri, Jul 29, 2011 at 2:03 AM, Otis Gospodnetic \< > > > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > > > > > Hi, > > > > > I've read various information about the concept of Gateway in ES and > > > > I'm wondering what value Gateway adds when one is not deploying ES in > > > > a cloud? In a cloud like AWS local storage is not necessarily > > > > persistent - when you stop an EC2 instance I believe its local data is > > > > gone. But what if you are deploying ES to a set of your own servers > > > > where this is not the case? Which type of gw should one use? local? > > > > fs? > > > > > ## Thanks, Otis > > > > > > > > Sematext is hiring search engineers - > > > > [Jobs](http://sematext.com/about/jobs.html) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 29, 2011, 8:30pm UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/6 "2011-07-29T20:30:44Z")
Yes, that is the most common case. Another use case is for cases where an in memory index is used, but long term persistency is still desirable in a write behind fashion. Note that even with the ec2 and local storage its not a clear cut. You can still use local gateway with a high replica account, if you are ok with the fact that if (number\_of\_replicas + 1) nodes are wiped out, you need to reindex the data. -shay.banon On Fri, Jul 29, 2011 at 11:10 PM, Otis Gospodnetic \< [otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)\> wrote: > Hi, > > Would it then be true to say that pretty much the only (or at least > the main) scenario where Shared FS gw makes more sense over the Local > gw is when one is dealing with servers whose local storage is > ephemeral/temporary, as is the case in EC2? > > ## Thanks, Otis > > Sematext is hiring search engineers - [Jobs - Sematext](http://sematext.com/about/jobs.html) > > On Jul 29, 6:33 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Thats stored on all the eligible master nodes (which in a default config, > > its all nodes). > > > > On Fri, Jul 29, 2011 at 11:35 AM, Otis Gospodnetic \< > > > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > > > Thanks Shay. > > > > > In case of "local" all index data stays local spread over N replicas > > > and M shards. > > > And the index settings/configs/mappings/state/etc. is all stored > > > locally (on local disks), right? And what about replicas of this > > > data? Is this stored in 1 central place or are there copies/replicas > > > of index settings/configs/mappings/state/etc. on multiple cluster > > > nodes? I couldn't find this stated in the guide or anywhere else. > > > > > ## Thanks, Otis > > > > > > Sematext is hiring search engineers - > > > [Jobs - Sematext](http://sematext.com/about/jobs.html) > > > > > On Jul 29, 2:19 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > > local, the default, is the recommended one, and actually it is also > > > > the > > > > one > > > > being used in most cases in cloud environments as well. > > > > > > On Fri, Jul 29, 2011 at 2:03 AM, Otis Gospodnetic \< > > > > > > [otis.gospodne...@gmail.com](mailto:otis.gospodne...@gmail.com)\> wrote: > > > > > > > > > Hi, > > > > > > > I've read various information about the concept of Gateway in ES > > > > > and > > > > > I'm wondering what value Gateway adds when one is not deploying ES > > > > > in > > > > > a cloud? In a cloud like AWS local storage is not necessarily > > > > > persistent - when you stop an EC2 instance I believe its local data > > > > > is > > > > > gone. But what if you are deploying ES to a set of your own > > > > > servers > > > > > where this is not the case? Which type of gw should one use? > > > > > local? > > > > > fs? > > > > > > > ## Thanks, Otis > > > > > > > > > > Sematext is hiring search engineers - > > > > > [Jobs - Sematext](http://sematext.com/about/jobs.html) ---
**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, 3:58am UTC](https://discuss.elastic.co/t/value-of-gateway-in-non-cloud-environments/4991/7 "2017-07-06T03:58:48Z")