Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog post:
http://www.elasticsearch.org/blog/2011/11/16/0.18.3-released.html.
-shay.banon
Heads up that this release includes a broken plugin script, the fix is
simple (Broken plugin script · Issue #1474 · elastic/elasticsearch · GitHub).
On Wed, Nov 16, 2011 at 3:43 PM, Shay Banon kimchy@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog
post: Elasticsearch Platform — Find real-time answers at scale | Elastic.-shay.banon
0.18.4 has been released fixing the plugin script.
On Wed, Nov 16, 2011 at 9:04 PM, Shay Banon kimchy@gmail.com wrote:
Heads up that this release includes a broken plugin script, the fix is
simple (Broken plugin script · Issue #1474 · elastic/elasticsearch · GitHub).On Wed, Nov 16, 2011 at 3:43 PM, Shay Banon kimchy@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog
post: Elasticsearch Platform — Find real-time answers at scale | Elastic.-shay.banon
superspeed~
From: Shay Banon
Sent: Thursday, November 17, 2011 4:05 AM
To: elasticsearch@googlegroups.com
Subject: Re: 0.18.3 Released
0.18.4 has been released fixing the plugin script.
On Wed, Nov 16, 2011 at 9:04 PM, Shay Banon kimchy@gmail.com wrote:
Heads up that this release includes a broken plugin script, the fix is simple (https://github.com/elasticsearch/elasticsearch/issues/1474).
On Wed, Nov 16, 2011 at 3:43 PM, Shay Banon kimchy@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog post: http://www.elasticsearch.org/blog/2011/11/16/0.18.3-released.html.
-shay.banonHi Shay
In case I want to upgrade a cluster running ES 0.17.x, having
different type of clients (6 servers connected as Node clients and 2
as Transport) with the same library version, would it be necessary to
update client nodes to 0.18.x as well or they can live togheter for a
while?.
I guess Transport clients may not be affected but I'm worried about
Node ones.
Cheers,
On 16 nov, 10:43, Shay Banon kim...@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog post:Elasticsearch Platform — Find real-time answers at scale | Elastic.
-shay.banon
Yes, if you upgrade the server to 0.18, you will need to upgrade the
clients (both transport and node) to 0.18 as well.
On Thu, Nov 17, 2011 at 10:28 PM, Frederic focampo.br@gmail.com wrote:
Hi Shay
In case I want to upgrade a cluster running ES 0.17.x, having
different type of clients (6 servers connected as Node clients and 2
as Transport) with the same library version, would it be necessary to
update client nodes to 0.18.x as well or they can live togheter for a
while?.I guess Transport clients may not be affected but I'm worried about
Node ones.Cheers,
On 16 nov, 10:43, Shay Banon kim...@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog
post:Elasticsearch Platform — Find real-time answers at scale | Elastic.-shay.banon
Cool, as always thanks for your help and time.
On 20 nov, 05:02, Shay Banon kim...@gmail.com wrote:
Yes, if you upgrade the server to 0.18, you will need to upgrade the
clients (both transport and node) to 0.18 as well.On Thu, Nov 17, 2011 at 10:28 PM, Frederic focampo...@gmail.com wrote:
Hi Shay
In case I want to upgrade a cluster running ES 0.17.x, having
different type of clients (6 servers connected as Node clients and 2
as Transport) with the same library version, would it be necessary to
update client nodes to 0.18.x as well or they can live togheter for a
while?.I guess Transport clients may not be affected but I'm worried about
Node ones.Cheers,
On 16 nov, 10:43, Shay Banon kim...@gmail.com wrote:
Heya,
0.18.3 (and 0.17.10) have just been released. More info in the blog
post:Elasticsearch Platform — Find real-time answers at scale | Elastic.-shay.banon