# Elasticsearch deployment

**URL:** <https://discuss.elastic.co/t/elasticsearch-deployment/276700>\
**Category:** Elasticsearch\
**Created:** [June 22, 2021, 7:49pm UTC](https://discuss.elastic.co/t/elasticsearch-deployment/276700 "2021-06-22T19:49:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![porscheme](https://avatars.discourse-cdn.com/v4/letter/p/dfb087/32.png) [@porscheme](https://discuss.elastic.co/u/porscheme)\
**Post date:** [June 22, 2021, 7:49pm UTC](https://discuss.elastic.co/t/elasticsearch-deployment/276700/1 "2021-06-22T19:49:28Z")

</div>

We wanted to build Elasticsearch on cloud Azure.  
Source data size: 50TB  
Replicas count: 3  
Shard count: 1000

For doing this, we are considering below two VM SKUs.

1. L32sv2 is very processing we wanted to know SLAs for this VM SKU
2. Any experience with using this SKU is really helpful

DS5v2 – Intel Xeon processor  
RAM: 56 GB  
vCPU(s): 16  
Managed Disk: Premium SSD

L32s v2: AMD EPYC 7551 processor  
RAM: 256 GB  
vCPU(s): 32  
Local NVMe premium SSD disks attached to VMs (ephemeral)

---

<div class="post-metadata">

**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:** [June 22, 2021, 9:56pm UTC](https://discuss.elastic.co/t/elasticsearch-deployment/276700/2 "2021-06-22T21:56:14Z")

</div>

Welcome to our community! 😃

Are you saying you will have 2 nodes, with 3000 shards?

---

<div class="post-metadata">

**Author:** ![porscheme](https://avatars.discourse-cdn.com/v4/letter/p/dfb087/32.png) [@porscheme](https://discuss.elastic.co/u/porscheme)\
**Post date:** [June 25, 2021, 7:27am UTC](https://discuss.elastic.co/t/elasticsearch-deployment/276700/3 "2021-06-25T07:27:46Z")

</div>

No, we are thinking of using 10 nodes with 1000 shards.  
We want each shard to be 75GB.

But the real question here is...  
By default, I was assuming we’d have to use managed disks (using DS5v2 VM SKU) as we couldn’t rely on the local temporary storage. That could get blown up at any time. Attached managed storage seems to be the way most people talk about supporting this scenario online.

However, the Lsv2-series has both temporary storage and NVMe disk. The spec sheet for it talks about it being ideal for “Big Data, SQL, and NoSQL databases.”. Which seems to fit our problem space

Should use DS5v2 (with managed disks) or L32s (NVMe storage)

---

<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 23, 2021, 7:27am UTC](https://discuss.elastic.co/t/elasticsearch-deployment/276700/4 "2021-07-23T07:27:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.