curl -X POST "http://localhost:9200/_reindex" -H 'Content-Type: application/json' -d'
{
"source": {
"remote": {
"host": "http://remoteip:9200"
},
"index": "mylogs-2019.06.17" <---- Remote cluster index
},
"dest": {
"index": "mylogs-2019.06.17" <---- Local Index
}
}'
{"error":{"root_cause":[{"type":"x_content_parse_exception","reason":"[7:18] [reindex] failed to parse field [source]"}],"type":"x_content_parse_exception","reason":"[7:18] [reindex] failed to parse field [source]","caused_by":{"type":"json_parse_exception","reason":"Unexpected character ('<' (code 60)): was expecting comma to separate Object entries\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@58cd6dfa; line: 7, column: 49]"}},"status":400}
Can anyone advise how to fix this? Ive tried content type text/plain but apparently this is not supported.
If I am reindexing from a single node ELK stack to a Multi-node Elastic search cluster.
Which node on the elastic search cluster do I do this from?, One of the dedicated master nodes, or one of the dedicated data nodes?
Obviously I want the data I am reindexing to be spread out across the cluster, and not just dumped onto one of the nodes, is this a concern, or will elasticsearch just do this naturally?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.