lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Schaum Mallik <>
Subject Re: SolrCoreInitializationException after restart of one solr node
Date Thu, 20 Sep 2018 14:22:57 GMT
Thanks for the response Shawn.

My follow up question is how would the zookeeper ensemble know that the
location of the indexes has changed? Also do I need to apply the same
changes to the other 2 solr nodes which are working fine?

On Thursday, September 20, 2018, Shawn Heisey <> wrote:

> On 9/20/2018 6:02 AM, Schaum Mallik wrote:
>> Yeah my indexes, read and write works fine on the other two solr nodes.
>> Since I have this setup running in prod currently what are the steps you
>> will advice I take to resolve this issue. Starting from scratch is really
>> not an option since it will involve a huge cost. Is there some workaround
>> that you guys can suggest.
>> when you say move the instance dir outside the /op/solr are you
>> suggesting,
>> modifying this value 'SOLR_HOME'?
> No, I mean literally moving the directory somewhere else. Something like
> this:
> mkdir /tmp/index-keep
> mv /opt/solr/server/solr/configsets/articles /tmp/index-keep/.
> mv /opt/solr/server/solr/configsets/categories /tmp/index-keep/.
> # move any other non-cloud cores out
> # restart Solr here
> Thanks,
> Shawn

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message