# Machine Learning Functionality Across Clusters **URL:** \ **Category:** SIEM\ **Created:** [April 15, 2022, 4:51pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514 "2022-04-15T16:51:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Datt\_Mamon](https://avatars.discourse-cdn.com/v4/letter/d/e480ec/32.png) [@Datt\_Mamon](https://discuss.elastic.co/u/Datt_Mamon)\ **Post date:** [April 15, 2022, 4:51pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514/1 "2022-04-15T16:51:58Z")
Hello Elastic Community! Running into an issue in my environment that I was hoping y'all could help with. My current architecture is divided into 3 clusters: RED1, BLUE1, and my Cross Cluster Search (CCS) cluster that has my CCS node and my Kibana node running on it. I have a Machine Learning node on RED1, but I can't get my CCS cluster, and by extension my Kibana, to read that there is an ML node out on RED1. NOTE: Everything else is flowing between these clusters, only thing that is hung up is this ML thing. Looking at it from the Kibana in RED1 I can utilize ML, but the "production" Kibana is the one out on the CCS cluster, not on RED1. Xpack.ml.enabled is set to 'true' on every node in each cluster. Any tips would be appreciated! Thank you! ---
**Author:** ![spong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spong/32/54343_2.png) [@spong](https://discuss.elastic.co/u/spong)\ **Post date:** [April 15, 2022, 5:38pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514/2 "2022-04-15T17:38:33Z")
Hey there @Datt_Mamon! 👋 Does your ML node happen to have `remote_cluster_client` configured as well? [Related docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#ml-node). Cheers! Garrett ---
**Author:** ![Datt\_Mamon](https://avatars.discourse-cdn.com/v4/letter/d/e480ec/32.png) [@Datt\_Mamon](https://discuss.elastic.co/u/Datt_Mamon)\ **Post date:** [April 15, 2022, 6:17pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514/3 "2022-04-15T18:17:37Z")
Just double-checked: yes, it does. ---
**Author:** ![spong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spong/32/54343_2.png) [@spong](https://discuss.elastic.co/u/spong)\ **Post date:** [April 15, 2022, 7:33pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514/4 "2022-04-15T19:33:07Z")
Okie, so I double checked with someone on the ML side, and apparently there is no notion of `Remote ML Job`'s, just `Remote Search Indices`, which while not super clear, I suppose can be sussed out from [this documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-settings.html#general-ml-settings): > If you want to run machine learning jobs, there must be at least one machine learning node in your cluster. i.e. meaning you can only access ML Job's from Kibana nodes within the same cluster. That said, it sounds like your CCS Kibana should be able to access the resulting indices from any ML Jobs/Transforms on the `RED1` cluster, but you just can't do management actions from those other clusters. So if they need to be managed from your main CCS Kibana, you'll want to move the ML Node to that cluster. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 13, 2022, 7:33pm UTC](https://discuss.elastic.co/t/machine-learning-functionality-across-clusters/302514/5 "2022-05-13T19:33:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.