I would just start another node (or a couple of nodes for security reasons,
mantaining replicas in different machines, etc.) in your cluster with the
new ES version, wait untill data gets copied, turn off every deprecated
(old) version of ES and then restart the nodes you turned-off with after
If you wish, I can prepare a knapsack backport for 0.20, then you can dump
all your data into an archive file, and reimport the archive into a higher
version.
Jörg
On Thu, Oct 2, 2014 at 2:28 AM, Eugene Strokin eug...@strokin.info wrote:
Hello,
my ES cluster is still running version 0.20.1.
FYI I have prepared Knapsack plugin for Elasticsearch 0.20.6
https://github.com/jprante/elasticsearch-knapsack
Source code tag:
https://github.com/jprante/elasticsearch-knapsack/releases/tag/0.20.6.2
Link of Plugin ZIP for 0.20.6.2:
Your indices should be fine as is. Lucene is guaranteed to be able to read
data from 1 major revision prior. Elasticsearch 0.20 is Lucene 3 and the
latest Elasticsearch is Lucene 4. Because of various bugs at the Lucene
level, you should run an optimize (normally discouraged) to upgrade the
Hello,
my ES cluster is still running version 0.20.1. It is time to upgrade. I
know I cannot just use indexes as is and replace the jars by the newest ES.
They are not compatible as far as I understood.
So I need to set up a parallel cluster with the newest ES and some how
transfer all the data
