Reindex from remote to cloud fails "Connection reset by peer"

Hello,

I try to reindex from a remote cluster to my elastic cloud cluster like this:

POST _reindex
{
  "conflicts": "proceed",
  "source": {
    "remote": {
      "host": "http://aaa.mysite.com:9200",
      "username": "elastic",
      "password": "XXXXX"
    },
    "index": ".reporting-2018.04.29"
  },
  "dest": {
    "index": ".reporting-2018.04.29",
    "version_type": "external"
  }
}

Here is the response:

{
  "error": {
    "root_cause": [
      {
        "type": "i_o_exception",
        "reason": "Connection reset by peer"
      }
    ],
    "type": "i_o_exception",
    "reason": "Connection reset by peer"
  },
  "status": 500
}

I understand here that I do not need to set reindex.remote.whitelist. I tried, same effect anyway

On my on-premise cluster (the remote), I have added the cloud cluster in the

PUT /_cluster/settings
{
    "persistent" : {
        "xpack.security.transport.filter.allow" : 
        [
              "theclusterid.eu-west-1.aws.found.io"
            ]
    }
}

By the way the cluster is accessible:

> curl "http://elastic:XXXXX@aaa.mysite.com:9200"
{
  "name" : "XXXX",
  "cluster_name" : "XXXXX",
  "cluster_uuid" : "wK4ED2gSRpeytWzJPFbOhA",
  "version" : {
    "number" : "6.2.2",
    "build_hash" : "10b1edd",
    "build_date" : "2018-02-16T19:01:30.685723Z",
    "build_snapshot" : false,
    "lucene_version" : "7.2.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

Can anybody help me for that? is there some logs somewhere?

Found that the problem is xpack transport filtering. When doing the reindex from the cloud, what is the IP address that will perform the reindex? seems not to be theclusterid.eu-west-1.aws.found.io

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.