You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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!
The text was updated successfully, but these errors were encountered: