Reindex to remote server


(Jonar B) #1

Is there any chance to reindex to remote server?
The destination will be the remote.

supposedly like this...

POST 192.168.200.250:9200/_reindex
    {
      "source": {
        "index": "es_xfer",
        "query": {
          "match_all": {
          }
        }
      },
      "dest": {
        "remote": {
    	  "host": "192.168.200.249:9200"
    	},
        "index": "sample"
      }
    }

(Alexander Reelsen) #2

Hey,

you can only pull in data from a remote source, not indexing into a remote source. However this shouldnt be a problem, you just have to execute the reindex from the other cluster?

--Alex


(Jonar B) #3

So it is not possible? or there's another workaround?

Sorry but the other cluster doesn't have a public ip.


(Aaron Mildenstein) #4

VPNs and routing could still make that accessible, but barring that, other options include having both clusters share a snapshot repository (probably S3, so it could be accessible to both), and snapshotting from one cluster, and restoring to the other.


(Jonar B) #5

Is there a way which I can store my repository to a remote server?


(Aaron Mildenstein) #6

In order to be a shared repository, both clusters would need to be able to read/write to the same shared filesystem. This is why I recommended S3, as it's the most secure option for external storage that works as a repository for Elasticsearch.


(Jonar B) #7

Yes, I could use S3 but it is not free. :joy:
Anyway, thank you for your input @theuntergeek.


(system) #8

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