3

I'm trying to run a simple code example to train and predict a ML algorithm using the Opensearch ML Commons plugin on a AWS managed Opensearch cluster. The cluster is on OS version 2.5, which definitely supports the plugin. The code example can be found here .

When I run the sample code in my console I get the following error message:

"type": "m_l_resource_not_found_exception",
    "reason": "No eligible node found to execute this request. It's best practice to provision ML nodes to serve your models. You can disable this setting to serve the model on your data node for development purposes by disabling the \"plugins.ml_commons.only_run_on_ml_node\" configuration using the _cluster/setting api"

However after trying to update the settings I get _cluster/settings payload not allowed, it doesn't seem like the AWS OS version supports the cluster/settings API except for these

/_cluster/settings for several properties:

action.auto_create_index

action.search.shard_count.limit

indices.breaker.fielddata.limit

indices.breaker.request.limit

indices.breaker.total.limit

cluster.max_shards_per_node

source

A few questions:

  1. Am I correct in my assumption that I can't update this cluster setting, meaning that I can't run ML Commons on an AWS version of Opensearch
  2. Is there a way to configure an ML node on a AWS OS. All examples seen require you to update the opensearch.yml file, which I can't do because I'm using a hosted version.
  3. Is there some security permission that I don't have that could allow me to change these cluster settings?

Thanks!

Yoni Levine
  • 51
  • 3
  • Did you find a solution to this? I was able to update the `only_run_on_ml_node` setting by doing PUT `{"persistent": {"plugins.ml_commons.only_run_on_ml_node": false}}`, up until they released version `OpenSearch_2_5_R20230308-P4`. Now I'm getting 401 with the "not allowed" message you shared. – LondonAppDev Jun 06 '23 at 10:19
  • Hi, I see you're new to SO. If you feel an answer solved the problem, please mark it as 'accepted' by clicking the green check mark. This helps keep the focus on older SO which still don't have answers. – fucalost Jun 25 '23 at 16:50

2 Answers2

0

Amazon OpenSearch Service supports ML Commons for versions >= 1.3

One of three things is likely occurring here:

  1. Instance Types: certain operations (e.g. anomaly detection, ML Commons) are not supported on all instances. While AWS do not specify which instances are supported for ML Commons, it is likely that t2.micro and t2.small nodes will not be supported — this is the case with anomaly detection.

  2. Access Control: you must enable fine-grained access control (FGAC) in order to use non-standard plugins. kNN, SQL, and other CRUD-oriented actions, of course, are supported without FGAC. Although there is no documentation to confirm this, I imagine that ML Commons, as with Anomaly Detection, requires FGAC as the plugin involves significant modifications to cluster/node configuration.

    • Additionally, you’ll need to map the ml_full_access backend role to your user, even if you already have the all_access role. More on this here.

  3. Formatting of _settings API call: Amazon’s flavour of OpenSearch requires “PUT requests to the _cluster/settings API that use the "flat" settings form” [source]

fucalost
  • 313
  • 1
  • 8
0

Notice Neural Search is an experimental feature, you can send an email to semantic-search@amazon.com to enable Neural Search feature for your account as explained in this link.

dhanielo
  • 23
  • 2
  • 7