Improve exception handling when master node is missing remote_cluster_client role #121149
Labels
>bug
:Distributed Coordination/Cluster Coordination
Cluster formation and cluster state publication, including cluster membership and fault detection.
Team:Distributed Coordination
Meta label for Distributed Coordination team
Elasticsearch Version
8.18.0, 9.0.0
Installed Plugins
No response
Java Version
bundled
OS Version
Linux
Problem Description
When the master node doesn't have the
remote_cluster_client
role, and CCS is used, thenRemoteClusterLicenseChecker.remoteClusterAliases
will returnno_such_remote_cluster_exception,
which is misleading.There's probably a bug in
ClusterNameExpressionResolver
. We should be reporting this as anIllegalArgumentException
as we do inRemoteClusterService
.Steps to Reproduce
remote_cluster_client
, while the ML node has (probably ECK config)Logs (if relevant)
Here is an exemplary error stack trace:
The text was updated successfully, but these errors were encountered: