Thank you :)
On Tuesday, December 30, 2014 3:08:51 PM UTC+1, rcmuir wrote:
>
> Yes. again, use the latest version (1.4.x). its very simple.
>
> On Tue, Dec 30, 2014 at 8:53 AM, Georgeta Boanea > wrote:
> > The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
> > using Lucen
Yes. again, use the latest version (1.4.x). its very simple.
On Tue, Dec 30, 2014 at 8:53 AM, Georgeta Boanea wrote:
> The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
> using Lucene 3.6, is it the same bug?
>
>
> On Tuesday, December 30, 2014 2:08:48 PM UTC+1, Robert Muir
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
using Lucene 3.6, is it the same bug?
On Tuesday, December 30, 2014 2:08:48 PM UTC+1, Robert Muir wrote:
>
> This bug occurs because you are upgrading to an old version of
> elasticsearch (1.3.4). Try the latest version wh
This bug occurs because you are upgrading to an old version of
elasticsearch (1.3.4). Try the latest version where the bug is fixed:
https://issues.apache.org/jira/browse/LUCENE-5975
On Fri, Dec 19, 2014 at 5:40 AM, Georgeta Boanea wrote:
> Hi All,
>
> After upgrading from ES 0.20.6 to 1.3.4 the
Any ideas?
On Friday, December 19, 2014 11:40:37 AM UTC+1, Georgeta Boanea wrote:
>
> Hi All,
>
> After upgrading from ES 0.20.6 to 1.3.4 the following messages occurred:
>
> [2014-12-19 10:02:06.714 GMT] WARN ||
> elasticsearch[es-node-name][generic][T#14]
> org.elasticsearch.cluster.action
Hi All,
After upgrading from ES 0.20.6 to 1.3.4 the following messages occurred:
[2014-12-19 10:02:06.714 GMT] WARN ||
elasticsearch[es-node-name][generic][T#14]
org.elasticsearch.cluster.action.shard [es-node-name] [index-name][3]
sending failed shard for [index-name][3], node[qOTLmb3IQC
