Skip to content

Remote cluster info returns fatally for invalid hostnames #35658

@jen-huang

Description

@jen-huang

I added a cluster with an invalid hostname:

PUT _cluster/settings
{
  "persistent": {
    "cluster": {
      "remote": {
        "jentest": {
          "seeds": [
            "testname:1234"
          ]
        }
      }
    }
  }
}

this is causing GET _remote/info to return fatally

{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "unknown host [testname]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "unknown host [testname]",
    "caused_by": {
      "type": "unknown_host_exception",
      "reason": "testname: nodename nor servname provided, or not known"
    }
  },
  "status": 400
}

For our Remote Clusters management UI feature, we're using _remote/info to fetch the list and info of clusters for display. Ideally it would still return the list of all clusters, maybe with the error attached to the corresponding cluster.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions