ElasticSearch: Migrate from 0.20.5 to 1.5.2 - single node - suggested steps? -
we have been sooooo happy our es rig, haven't thought upgrade it... need to.
we run 0.20 on centos. single, stand alone es system.
we see code related changes 0.9 1.x, , have under control.
what best steps rig current? (we set 2nd server alongside, if makes process cleaner.)
you're still running 0.20, wow!! if you're happy performance , capabilities of 0.20, you'll uber-delighted 1.5.2, sure!
before jumping upgrade, make sure check breaking changes pages. lot of things changed in 1.0 version , need make sure current assets (queries, client-side code, etc) adapted first. note starting es 1.2, dynamic scripting disabled default if used dynamic scripts you'll need take account , include script.disable_dynamic: false
in configuration, 0.20 far away might not have care that.
then, if check official upgrade guide, you'll see jumping many versions in 1 step, you'll need go through cluster restart, since have single node means service unavailable during upgrade. note bringing second node won't possible because pre-1.0 , post-1.0 versions not compatible.
once you're ready, i.e. you've been through breaking changes , adapted whatever need to, make sure back data before diving upgrade.
also make sure upgrade jdk @ least latest java 7, ideally java 8 if that's possible, or es 1.5.2 won't start.
then can shutdown node curl -xpost 'http://localhost:9200/_shutdown'
, upgrade es installation 1.5.2 , restart node.
after node has recovered , started, can upgrade indice files latest lucene format using curl -xpost 'http://localhost:9200/_upgrade'
.
disclaimer: note there many things changed between 0.2 , 1.5.2 might have missed some, points above should enough started. if can train in staging environment might able figure out , and smooth upgrade.
Comments
Post a Comment