Two related Solr issues

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Two related Solr issues

Mahesh Varma, Y. A.
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?

Will they be taken over by Master?

Please help me as I can find no info about this anywhere else. For info the core that is missing is of Sitecore analytics index.

solr<https://sitecore.stackexchange.com/questions/tagged/solr> analytics-index<https://sitecore.stackexchange.com/questions/tagged/analytics-index>


The error that Solr slave showing us for Analytics core is:


rg.apache.solr.common.SolrException: Error opening new searcher
        at org.apache.solr.core.SolrCore.<init>(SolrCore.java:815)
        at org.apache.solr.core.SolrCore.<init>(SolrCore.java:658)
        at org.apache.solr.core.CoreContainer.create(CoreContainer.java:637)
        at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:381)
        at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:375)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$1.run(ExecutorUtil.java:148)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
        at java.lang.Thread.run(Thread.java:748)


Can you please help us here why this happened? We could not find any info from the logs that is leading us to this error.




Thanks & Regards,

Y Mahesh Varma.

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com
Reply | Threaded
Open this post in threaded view
|

Re: Two related Solr issues

Shawn Heisey-2
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
Reply | Threaded
Open this post in threaded view
|

Re: Two related Solr issues

Jan Høydahl / Cominvent
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 <[hidden email]>:
>
>> 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