# Is it bad to disable mmapfs when running elasticsearch in fargate

**URL:** <https://discuss.elastic.co/t/is-it-bad-to-disable-mmapfs-when-running-elasticsearch-in-fargate/269044>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [April 1, 2021, 2:28pm UTC](https://discuss.elastic.co/t/is-it-bad-to-disable-mmapfs-when-running-elasticsearch-in-fargate/269044 "2021-04-01T14:28:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Heshan\_Anupama](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/heshan_anupama/32/86474_2.png) [@Heshan\_Anupama](https://discuss.elastic.co/u/Heshan_Anupama)\
**Post date:** [April 1, 2021, 2:28pm UTC](https://discuss.elastic.co/t/is-it-bad-to-disable-mmapfs-when-running-elasticsearch-in-fargate/269044/1 "2021-04-01T14:28:19Z")

</div>

Hello,  
I am trying to get elasticsearch with fargate and I am getting the error of [2]: max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]. I understand that we could not change the fargate host since we dont have access to it. However, I found that we could disable this. Is there any consequence of doing that as pointed in [here](https://stackoverflow.com/a/62860811/5901897) . Is it bad if I do it and use this in the production environment. Thank you.

---

<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:** [April 29, 2021, 2:28pm UTC](https://discuss.elastic.co/t/is-it-bad-to-disable-mmapfs-when-running-elasticsearch-in-fargate/269044/2 "2021-04-29T14:28:20Z")

</div>

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