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

Configuring ES with Docker documentation clarification #379

Open
rshen91 opened this issue Jun 18, 2019 · 1 comment
Open

Configuring ES with Docker documentation clarification #379

rshen91 opened this issue Jun 18, 2019 · 1 comment

Comments

@rshen91
Copy link

rshen91 commented Jun 18, 2019

Please let me know if this an appropriate place to post this request. I received a request to include an example in our docker documentation for defining four high-performance NVMe SSDs for the data volumes for an Elasticsearch master. Their working example on how to configure is:

  • path.data=/usr/share/elasticsearch/data1,/usr/share/elasticsearch/data2

    volumes:

  • /export/elasticsearch1a:/usr/share/elasticsearch/data1

  • /export/elasticsearch1b:/usr/share/elasticsearch/data1

Thank you!

@jeffkirk1
Copy link

Actually in the example above, I've defined only two drives, not four, but the principle is the same regardless of the number or type of drives. The point was that the documentation didn't describe how to override the default directory used for data in the Elasticsearch docker container. Splitting the data across multiple physical volumes is described for the native software installation elsewhere in the documentation. I just thought it would be convenient to include it with the Docker install instructions, since it's such a great way of boosting the IOPS for an Elasticsearch node. Works fine for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants