# Migration from ES 1.3.4 to ES 1.5.x **URL:** \ **Category:** Elasticsearch\ **Created:** [October 12, 2015, 10:55am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001 "2015-10-12T10:55:13Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 12, 2015, 10:55am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/1 "2015-10-12T10:55:13Z")
Hi, Currently, I got a ES cluster with datas on 1.3.4 version and I want to migrate them on a 1.5.x cluster. How do I proceed ? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [October 12, 2015, 10:57am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/2 "2015-10-12T10:57:21Z")
Do you want to upgrade the existing cluster in place or migrate the data to a new 1.5-based cluster? (You know that ES 1.7 has been out for quite a while, right?) ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 12, 2015, 12:39pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/3 "2015-10-12T12:39:29Z")
Yes I'd like to migrate the cluster (setup the new version) and migrate existing datas in the new cluster. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 12, 2015, 9:54pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/4 "2015-10-12T21:54:23Z")
You should really move to 1.7.2 as Magnus mentioned. Otherwise you have a few options; 1. Snapshot and restore the data 2. Disable allocation, add the new nodes to the existing cluster, migrate all data off the old nodes to the new ones 3. Reindex into the new cluster ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 13, 2015, 6:48am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/5 "2015-10-13T06:48:57Z")
Thank you for your answers. Just one more question : does "migrate all data" means to move the old base content in the directory defined by the parameter path.data ? For ex: if I defined in my old elasticsearch.yml "path.data" to "/data/es\_data", I could reconfigure this value on my new config file then add the disabled allocation option. I just simply copy all the files from {cluster\_name}/nodes/\* in the same directory than before but emptied Next, I add my nodes by starting ES. The data redindexation should be automatic. Is that correct or should I do this differently ? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 13, 2015, 7:00am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/6 "2015-10-13T07:00:19Z")
> [@nguafogu78](#): > > Just one more question : does "migrate all data" means to move the old base content in the directory defined by the parameter path.data ? You could do that, but it won't reindex anything. ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 13, 2015, 7:44am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/7 "2015-10-13T07:44:24Z")
All right. What do you suggest instead. Could you also give me some command examples please ? Thank you ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 13, 2015, 8:33am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/8 "2015-10-13T08:33:08Z")
This is how I reindex, with Logstash - [https://gist.github.com/markwalkom/8a7201e3f6ea4354ae06](https://gist.github.com/markwalkom/8a7201e3f6ea4354ae06) ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 13, 2015, 9:57am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/9 "2015-10-13T09:57:22Z")
Thanks, How do I make sure every data is migrated. Is there a command to check that out ? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 13, 2015, 9:58am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/10 "2015-10-13T09:58:37Z")
You can look at `_cat/count`, or just `_count`. ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [October 13, 2015, 10:11am UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/11 "2015-10-13T10:11:06Z")
I meant that it seems logstash needs to be running a lot of time before everything is migrated. Therefore, I was wondering if the way you launch logstash matters. Do you execute it in backend ? Here's my command so far: /opt/logstash/bin/logstash -f config\_file.conf -l /var/log/logstash/reindex\_es.log --debug --verbose Unfortunately it's only when I launched it manually to get the number of input increase: {:timestamp=\>"2015-10-13T11:47:58.814000+0200", :message=\>"Pipeline shutdown complete.", :level=\>:info, :file=\>"logstash/pipeline.rb", :line=\>"89"} {:timestamp=\>"2015-10-13T11:50:30.603000+0200", :message=\>"Pipeline shutdown complete.", :level=\>:info, :file=\>"logstash/pipeline.rb", :line=\>"89"} {:timestamp=\>"2015-10-13T11:53:25.538000+0200", :message=\>"Pipeline shutdown complete.", :level=\>:info, :file=\>"logstash/pipeline.rb", :line=\>"89"} {:timestamp=\>"2015-10-13T12:03:51.620000+0200", :message=\>"Pipeline shutdown complete.", :level=\>:info, :file=\>"logstash/pipeline.rb", :line=\>"89"} {:timestamp=\>"2015-10-13T12:05:18.470000+0200", :message=\>"Pipeline shutdown complete.", :level=\>:info} ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 13, 2015, 8:08pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/12 "2015-10-13T20:08:05Z")
Ahh right, well it should just stop once it's done the last document. ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [November 2, 2015, 10:33pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/13 "2015-11-02T22:33:39Z")
That's my problem : it doesn't seem when it stops that every data is migrated, each time I execute it new data incomes... Is there a problem with the way I proceed ? Thank for you time ---
**Author:** ![nguafogu78](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@nguafogu78](https://discuss.elastic.co/u/nguafogu78)\ **Post date:** [November 4, 2015, 1:10pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/14 "2015-11-04T13:10:25Z")
By the way, does the method change if we want to change ES 1.3.4 to 1.7.3 (so we could use Kibana 4.1.2) ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:40pm UTC](https://discuss.elastic.co/t/migration-from-es-1-3-4-to-es-1-5-x/32001/15 "2017-07-05T23:40:39Z")