-
Notifications
You must be signed in to change notification settings - Fork 61
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
Update DEVELOPER_GUIDE.md #113
Update DEVELOPER_GUIDE.md #113
Conversation
After navigating to OpenSearch Dashboards you should update the persistent settings for the cluster. The settings will update the behavior of the machine learning plugin, specifically the ml_commons plugin. ML Commons cluster settings: https://opensearch.org/docs/latest/ml-commons-plugin/cluster-settings/ | ||
|
||
You should paste this settings in the `Dev Tools` window and run it: | ||
|
||
```yml | ||
PUT /_cluster/settings | ||
{ | ||
"persistent" : { | ||
"plugins.ml_commons.only_run_on_ml_node" : false, | ||
"plugins.ml_commons.native_memory_threshold" : 100, | ||
"plugins.ml_commons.max_model_on_node": 20 | ||
} | ||
} | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After looking at it again, I feel like we should move it to theNext Steps
section, because this step is applicable after installing opensearch through way 1 (docker compose) or way 2 (tarball). So let's not put it under way 1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, thanks a lot for your guidance!
Thanks for solving the DCO issue. |
Signed-off-by: Merey <orazaly1508@gmail.com>
Signed-off-by: Merey <orazaly1508@gmail.com>
3461174
to
f2097e8
Compare
* Dev guide update Signed-off-by: Merey <orazaly1508@gmail.com> * Edited the developer guide Signed-off-by: Merey <orazaly1508@gmail.com> --------- Signed-off-by: Merey <orazaly1508@gmail.com> (cherry picked from commit f6cf39f)
* Dev guide update Signed-off-by: Merey <orazaly1508@gmail.com> * Edited the developer guide Signed-off-by: Merey <orazaly1508@gmail.com> --------- Signed-off-by: Merey <orazaly1508@gmail.com> (cherry picked from commit f6cf39f)
* Dev guide update Signed-off-by: Merey <orazaly1508@gmail.com> * Edited the developer guide Signed-off-by: Merey <orazaly1508@gmail.com> --------- Signed-off-by: Merey <orazaly1508@gmail.com> (cherry picked from commit f6cf39f) Co-authored-by: Merey <orazaly1508@gmail.com>
* Dev guide update Signed-off-by: Merey <orazaly1508@gmail.com> * Edited the developer guide Signed-off-by: Merey <orazaly1508@gmail.com> --------- Signed-off-by: Merey <orazaly1508@gmail.com> (cherry picked from commit f6cf39f) Co-authored-by: Merey <orazaly1508@gmail.com>
* Dev guide update Signed-off-by: Merey <orazaly1508@gmail.com> * Edited the developer guide Signed-off-by: Merey <orazaly1508@gmail.com> --------- Signed-off-by: Merey <orazaly1508@gmail.com>
Description
New contributors to the project have been facing an issue with nox testing, which has been causing delays and difficulties in their development process.
Issues Resolved
To address this, an update has been made to the Developer Guide that provides more detailed instructions before running nox tests and troubleshooting common errors. Specifically, during the office hour session, there was a discussion about updating the cluster settings.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.