[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-user
Subject:    Re: Two related Solr issues
From:       Jan_Høydahl <jan.asf () cominvent ! com>
Date:       2019-05-31 15:43:19
Message-ID: 660D6D19-0B9A-412C-B8B1-3F3CDA3AEA5D () cominvent ! com
[Download RAW message or body]

The sitecore app will get errors when that core is not found, and it is then up to \
the failover logic in sitecore to try the master. You should of course add back the \
missing core and let it sync up.

Sendt fra min iPad

> 31. mai 2019 kl. 17:05 skrev Shawn Heisey <apache@elyograg.org>:
> 
> > On 5/31/2019 7:50 AM, Mahesh Varma, Y. A. wrote:
> > Hi Team,
> > What happens to Sitecore - Solr query handling when a core is corrupted in Solr \
> > slave in a Master - slave setup? Our Sitecore site's solr search engine is a \
> > master-slave setup. One of the cores of the Slave is corrupted and is not \
> > available at all in Slave. It is not being replicated from Master too (Expecting \
> > index replication to do this but core is completely missing in Slave). As read in \
> > index replication documentation, all the queries are handled by Slave part of the \
> > set up. What happens to the queries that are handled by this core that is missing \
> > in slave?
> 
> We did not create the sitecore software.  We have no idea how they handle queries, \
> whether they have a load balancer, how that load balancer is configured if they do, \
> or other details that would be necessary to answer your question. 
> Solr itself has no ability to fail anything over in a master-slave setup.  That \
> must be handled elsewhere. 
> Thanks,
> Shawn


[prev in list] [next in list] [prev in thread] [next in thread]