# Sizing ES Gateways

**URL:** <https://discuss.elastic.co/t/sizing-es-gateways/6044>\
**Category:** Elasticsearch\
**Created:** [December 1, 2011, 8:47pm UTC](https://discuss.elastic.co/t/sizing-es-gateways/6044 "2011-12-01T20:47:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\
**Post date:** [December 1, 2011, 8:47pm UTC](https://discuss.elastic.co/t/sizing-es-gateways/6044/1 "2011-12-01T20:47:26Z")

</div>

Hi All,

Anyone have some practical guidance on sizing the disk space needed for ES  
gateways? If I have 100TB in indices and a replication factor of 3, I'd  
expect 300TB of indices in the cluster. What size should I expect my  
gateway data to take? What factors impact it? Specifically:

- Gateway Type - Guessing the Hadoop option depends on the replication  
factor
- 
# of Machines in Cluster
- Snapshot Frequency
- ...

If it's not an exact science, even some rule of thumb guidance would be  
helpful. Thanks,

--Mike

---

<div class="post-metadata">

**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:** [December 1, 2011, 9:25pm UTC](https://discuss.elastic.co/t/sizing-es-gateways/6044/2 "2011-12-01T21:25:35Z")

</div>

It depends on the gateway. First, regardless of the gateway used, the  
cluster will need the size itself (300tb in your case) among the nodes. If  
you use the local gateway, then you don't need any additional size, on full  
shutdown and restart, the cluster will restore its state from the local  
storage of each node (hence the name), where the replicas provides high  
availability. If you use a shared gateway (fs, hadoop, s3), then what  
happens is that the indices are snapshotted (copied) to the shred gateway,  
and the size required for that is the size of the "primary shards" (without  
replicas), in your case, 100TB.

I recommend to use local gateway, since it does not incur the overhead of  
"snapshotting".

-shay.banon

On Thu, Dec 1, 2011 at 10:47 PM, Michael Sick \<  
[michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com)\> wrote:

> Hi All,
> 
> Anyone have some practical guidance on sizing the disk space needed for ES  
> gateways? If I have 100TB in indices and a replication factor of 3, I'd  
> expect 300TB of indices in the cluster. What size should I expect my  
> gateway data to take? What factors impact it? Specifically:
> 
> - Gateway Type - Guessing the Hadoop option depends on the replication  
> factor
> - 
> # of Machines in Cluster
> - Snapshot Frequency
> - ...
> 
> If it's not an exact science, even some rule of thumb guidance would be  
> helpful. Thanks,
> 
> --Mike

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:46am UTC](https://discuss.elastic.co/t/sizing-es-gateways/6044/3 "2017-07-06T03:46:39Z")

</div>