Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ulimit should be increase for elasticsearch #93

Closed
clopnis opened this issue Jun 30, 2019 · 1 comment
Closed

Ulimit should be increase for elasticsearch #93

clopnis opened this issue Jun 30, 2019 · 1 comment
Assignees
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@clopnis
Copy link

clopnis commented Jun 30, 2019

Description

Elasticsearch is not able to start because max file descriptors is too low :

elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
Issue related here : docker-library/elasticsearch#140

Environment

  1. Opencti on Centos 7 running into LXC

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. get a node with # ulimit -n
    4096
  2. follow the docker install documentation sysctl -w vm.max_map_count=262144
  3. start # docker-compose up

Actual Output

Elasticsearch docker is restarting in loop with error following
elasticsearch_1 | [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]

Additional information

if you increase the ulimit on the pod, it works

# ulimit -n
65535

I don't know if it's better to add a check to have a large ulimit nofile on the documentation or to change the docker-compose.yml with something like on elasticsearch service :

ulimits:
    nofile:
       soft: 65536
       hard: 65536
@SamuelHassine SamuelHassine self-assigned this Jun 30, 2019
@SamuelHassine SamuelHassine added this to the Release 1.0.1 milestone Jun 30, 2019
@SamuelHassine
Copy link
Member

The docker-compose.yml file has been updated with new directives for running ElasticSearch in production.

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants