Document using xpack.ml.use_auto_machine_memory_percent setting in docker getting started #114009
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
shainaraskas
approved these changes
Oct 4, 2024
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
davidkyle
added
the
auto-backport
|
In the preview, the formatting for the code example I added is not right. I can't see what I did wrong, @shainaraskas can see what I'm missing please 
|
szabosteve
reviewed
Oct 9, 2024
szabosteve
reviewed
Oct 9, 2024
szabosteve
reviewed
Oct 9, 2024
szabosteve
reviewed
Oct 9, 2024
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
|
@elasticmachine update branch |
davidkyle
added a commit
to davidkyle/elasticsearch
that referenced
this pull request
Nov 8, 2024
…cker getting started (elastic#114009) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
davidkyle
added a commit
to davidkyle/elasticsearch
that referenced
this pull request
Nov 8, 2024
…cker getting started (elastic#114009) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 8, 2024
…cker getting started (#114009) (#116480) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 8, 2024
…cker getting started (#114009) (#116479) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
jozala
pushed a commit
that referenced
this pull request
Nov 13, 2024
…cker getting started (#114009) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
alexey-ivanov-es
pushed a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 28, 2024
…cker getting started (elastic#114009) If xpack.ml.use_auto_machine_memory_percent is not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model. This is useful for users wanting to get started with semantic search.The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables xpack.ml.use_auto_machine_memory_percent. For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
xpack.ml.use_auto_machine_memory_percentis not explicitly set to true then the default value (false) means ML will only use 30% of the available memory making it impractical to run the ELSER model without giving the container a huge amount of memory. Start local setsxpack.ml.use_auto_machine_memory_percent : truefor this reasonFor users wanting to get started with semantic search it is confusing that they cannot run an ml model in the container as instructed in the Install Elasticsearch with Docker guide.
The single node docker instructions have been updated with a command that gives the container enough memory to run the ELSER model and enables
xpack.ml.use_auto_machine_memory_percent.For the multi-node guide the docker compose file is updated to enable the ml setting for every node in the cluster. An alternative would be to make only 1 of the 3 nodes an ml node and apply the setting to that node only.