You should only roll forward with releases. I don't think downgrades are supported. 1.1 moved to a new version of lucene (4.7) and indices are not compatible with older versions of elastic search once you upgrade them. You shouldn't run clusters with mixed versions other than for the purpose of performing a rolling restart of the cluster during an upgrade.
In any case, when you perform an upgrade, you will want to use curl localhost:9200/_cluster/health?pretty=true to keep an eye on the cluster state. Basically as soon as you start or stop a node, the cluster will start rebalancing (depending on your replica settings) and you want to wait for that activity to stop before proceeding. Alternatively, you can temporarily change the balancing settings via the API. Basically my update process is as follows: verify current cluster status is green shut down a node wait for activity in the cluster to stabilize (no nodes initializing/relocating). upgrade the node start the node wait for activity to stabilize (no nodes initializing/relocating). only proceed to next node when cluster status is green again. If you do it like this, you should be able to do rolling restarts and upgrade. I've upgraded this way from 1.0.0 to 1.1.0 and recently to 1.1.1. I have a three node cluster with 2 replicas. So all nodes have all the data and no rebalancing happens when I remove a node and then re-add it. Also, if I take out a node, I still have a two instances of each shard. The cluster goes yellow when I take a node down for upgrading and as soon as I start the upgraded node it initializes and upgrades its shards in a few minutes and then the cluster goes green. Jilles On Friday, April 25, 2014 6:01:41 PM UTC+2, Srividhya Umashanker wrote: > > I am trying the rolling upgrade, which is expected to be fixed since ES > 1.0.0 release. > > While doing so, > > > - I have 3 Nodes running ES 1.1.1 > - I shutdown, one of those, and installed ES 1.0.3 > - Unlike early problems, when the ES 1.0.3 installed node starts, it > is seen in the cluster > - But, it does not share the shards/replicas of other nodes > > > > - Now, i reinstalled ES 1.1.1 in all appliances, and now the nodes are > shared. > > > Is this because I am installing ES 1.0.3 in a cluster running nodes with > ES 1.1.1? > > Runnng multiple versions of ES (1.0.0 and beyond) are expected to work > together? Please help > > > <https://lh4.googleusercontent.com/-XM4g7LuYMNw/U1qF0p-b4yI/AAAAAAAAAkU/NAgSmmIsGsI/s1600/es_multi_support.png> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/648d7e4a-a8b2-4014-bcbf-eb518bbf1bc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
