Skip to content

Commit

Permalink
Release version 1.4.1 (compatibility with elasticsearch 1.4.1)
Browse files Browse the repository at this point in the history 
Thanks to Danny Wilson (github.com/vizanto)
  • Loading branch information
@grmblfrz
grmblfrz committed Dec 15, 2014
1 parent cffc888 commit 9620416
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions README.textile
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,8 @@ h2. Compatibility
The following table shows the versions of elasticsearch and Apache Zookeeper that Zookeeper Plugin was built with.

|_. ES-zk Plugin |_. Elasticsearch |_. Zookeeper |
| master | 1.3.4 | 3.4.6 |
| master | 1.4.1 | 3.4.6 |
| 1.4.1 | 1.4.1 | 3.4.6 |
| 1.3.4 | 1.3.4 | 3.4.6 |
| 1.3.1 | 1.3.2 | 3.4.6 |
| 1.3.0 | 1.3.1 | 3.4.6 |
Expand All @@ -23,7 +24,7 @@ h3. Installation
* Install ZooKeeper plugin to ES by running

<pre>
% bin/plugin -url https://github.com/grmblfrz/elasticsearch-zookeeper/releases/download/v1.3.4/elasticsearch-zookeeper-1.3.4.zip -install zookeeper
% bin/plugin -url https://github.com/grmblfrz/elasticsearch-zookeeper/releases/download/v1.4.1/elasticsearch-zookeeper-1.4.1.zip -install zookeeper
</pre>

* Assuming that you are running ZooKeeper on the port 2181 (default), add the following lines to config/elasticsearch.yml file
Expand Down

4 comments on commit 9620416

@vizanto
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it actually work in practice?

@jloomis
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In practice I can't upgrade (rolling or not) to this without #2. With those changes it seems to mostly work but in testing it I've run into a situation where all shards can go unassigned on stopping the current master. Difficult to reproduce but scary enough that don't want to upgrade till I can track down the cause.

@grmblfrz
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I have successfully upgraded my clusters (even without #2) and they are working without problems. YMMV.

@jloomis
Copy link

@jloomis jloomis commented on 9620416 Jan 5, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whether you can do (non-rolling) upgrade without #2 depends on what's in your cluster state (e.g. if you have snapshot repositories configured) - since there are only version checks reading the state in a couple places if you don't hit one you're fine. As for the unassigned shards on bouncing master, still hard to reproduce but I've hit it twice now, though don't know that it came in with 1.4.1 vs earlier (we've been running 1.1.0 & haven't seen it, but also don't restart nodes frequently.) On plus side recovery is kicked off if you subsequently stop another node, but...

Please sign in to comment.