Any ideas?
On Wednesday, December 31, 2014 3:35:39 PM UTC+1, Georgeta wrote:
>
> Hi All,
>
> I have a 5 nodes cluster. I updated the cluster from 0.20.6 to 1.4.2.
> When I start the cluster with shard allocation disabled, it starts and
> goes into a yellow state, all good. W
a:1527)
at
org.elasticsearch.index.engine.internal.InternalEngine.start(InternalEngine.java:309)
... 6 more
Is there a way to resolve the checksum problem? Any idea why the files are
deleted?
Any help would be greatly appreciated :)
Thank you
Georgeta
--
You received this message because you are subscri
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
t 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 following messages occurred:
>
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-nod
/localhost:48012/index-name/_optimize?max_num_segments=1) for the
index before the update, everything is fine. Optimize works just before the
update, if is done after the update the problem remains the same.
Any idea why this problem occurs?
Is there another way to avoid this problem? I want t
