Set explicit limits on elasticsearch file descriptors (#7788)

Co-authored-by: Dustin Ingram <[email protected]>
pypi · Apr 10, 2020 · 9019b5e · 9019b5e
1 parent c488578
commit 9019b5e
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -27,6 +27,10 @@ services:
     image: docker.elastic.co/elasticsearch/elasticsearch:6.8.7
     environment:
       - xpack.security.enabled=false
+    ulimits:
+      nofile:
+        soft: 65536
+        hard: 65536
 
   camo:
     image: pypa/warehouse-camo:latest

diff --git a/docs/development/getting-started.rst b/docs/development/getting-started.rst
@@ -164,7 +164,7 @@ application.
 
    If you are using Linux, you may need to configure the maximum map count to get
    the `elasticsearch` up and running. According to the
-   `documentation <https://www.elastic.co/guide/en/elasticsearch/reference/6.2/vm-max-map-count.html>`_
+   `documentation <https://www.elastic.co/guide/en/elasticsearch/reference/6.8/vm-max-map-count.html>`_
    this can be set temporarily:
 
    .. code-block:: console
@@ -177,7 +177,7 @@ application.
    Also check that you have more than 5% disk space free, otherwise
    elasticsearch will become read only. See ``flood_stage`` in the
    `elasticsearch disk allocation docs
-   <https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html>`_.
+   <https://www.elastic.co/guide/en/elasticsearch/reference/6.8/disk-allocator.html>`_.
 
 
 Once ``make build`` has finished,  run the command: