(RecoveryStrategy.java:199)
at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:388)
at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:220)
Thanks,
Balaji
--
View this message in context:
http://lucene.472066.n3.nabble.com/Nodes-cannot-recover-and-become
: Nodes cannot recover and become unavailable
also, did you re create the cluster after upgrading to a newer
version? I believe there were some changes made to the
clusterstate.json recently that are not backwards compatible.
--
Sami Siren
On Wed, Sep 19, 2012 at 6:21 PM
Hi - at first i didn't recreate the Zookeeper data but i got it to work. I'll
check the removal of the LOG line.
thanks
-Original message-
From:Sami Siren ssi...@gmail.com
Sent: Wed 19-Sep-2012 17:45
To: solr-user@lucene.apache.org
Subject: Re: Nodes cannot recover and become
Hi,
Since the 2012-09-17 11:10:41 build shards start to have trouble coming back
online. When i restart one node the slices on the other nodes are throwing
exceptions and cannot be queried. I'm not sure how to remedy the problem but
stopping a node or restarting it a few times seems to help
Hi,
I am having troubles understanding the reason for that NPE.
First you could try removing the line #102 in HttpClientUtility so
that logging does not prevent creation of the http client in
SyncStrategy.
--
Sami Siren
On Wed, Sep 19, 2012 at 5:29 PM, Markus Jelsma
markus.jel...@openindex.io
also, did you re create the cluster after upgrading to a newer
version? I believe there were some changes made to the
clusterstate.json recently that are not backwards compatible.
--
Sami Siren
On Wed, Sep 19, 2012 at 6:21 PM, Sami Siren ssi...@gmail.com wrote:
Hi,
I am having troubles
bq. I believe there were some changes made to the clusterstate.json
recently that are not backwards compatible.
Indeed - I think yonik committed something the other day - we prob
should send an email out about this. Not sure exactly how easy an
upgrade is or what steps to take - it may be
On Wed, Sep 19, 2012 at 4:25 PM, Mark Miller markrmil...@gmail.com wrote:
bq. I believe there were some changes made to the clusterstate.json
recently that are not backwards compatible.
Indeed - I think yonik committed something the other day - we prob
should send an email out about this.