Migration from ES 1.3.4 to ES 1.5.x


(AHL) #1

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 ?


(Magnus B├Ąck) #2

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?)


(AHL) #3

Yes I'd like to migrate the cluster (setup the new version) and migrate existing datas in the new cluster.


(Mark Walkom) #4

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

(AHL) #5

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 ?


(Mark Walkom) #6

You could do that, but it won't reindex anything.


(AHL) #7

All right.

What do you suggest instead. Could you also give me some command examples please ?

Thank you


(Mark Walkom) #8

This is how I reindex, with Logstash - https://gist.github.com/markwalkom/8a7201e3f6ea4354ae06


(AHL) #9

Thanks,

How do I make sure every data is migrated. Is there a command to check that out ?


(Mark Walkom) #10

You can look at _cat/count, or just _count.


(AHL) #11

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}


(Mark Walkom) #12

Ahh right, well it should just stop once it's done the last document.


(AHL) #13

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


(AHL) #14

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) ?


(system) #15