Remote reindex from 1.3.9 to 5.5


(Patrick) #1

I want to migrate elasticsearch from 1.3.9 to 5.5 . So i decided to use the second option from the doc.

Install a 5.5 , create index( with settings and mapping) and do a remote reindex.

Actually i don't have any error but i still have in my new server o created index after doing the reindex.

Here the result : "took": 30, "timed_out": false, "total": 0, "updated": 0, "created": 0, "deleted": 0, "batches": 0, "version_conflicts": 0, "noops": 0, "retries": { "bulk": 0, "search": 0 }, "throttled_millis": 0, "requests_per_second": -1, "throttled_until_millis": 0, "failures": [] }

Do you have any idea to resolve or which log to look at ?

The command

{
"source": {
"remote": {
"host": "http://localhost:9200",
"username": "elastic",
"password": "changeme"
},
"index": "myindex"
},
"dest": {
"index": "mynewindex"
}
}


(Yosi) #2

I am trying this migration path
upgrade from 1.7.x to 2.x

then to 5.x

Still stumbling in the dark, but just in case it helps you


(Mujtaba Hussain) #3

It's not going to be simple either way unfortunately. :frowning: I tried to upgrade from "2.4.2" to 5.0 when it first came out using the above mentioned steps, but it would always fail on geo_point fields. :frowning:


(Patrick) #4

Thanks for your feedback


(Yosi) #5

ok for me I believe I am much closer to a solution than where I started. When doing the upgrade using this doc

https://www.elastic.co/guide/en/elasticsearch/reference/2.4/rolling-upgrades.html#upgrade-node

It will tell you in detail the error you are encountering in the log directory. using that I am now closer to resolving my upgrade.

In case it helps anyone


(system) #6

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