Is your Sitecore Content Management and Content Delivery Server down? Well the reason being you have configured your Sitecore installation to use SOLR as a search platform and the SOLR server itself is down. What? Seriously…. SOLR server triggers a DOMINO effect on the CM and CD servers if it is down. Something we would not want to happen in a production environment. We faced this issue few days back on one of our QA environment. The best way out was to contact Sitecore Support who then reported it as a bug and provided a solution which I am sharing it here.
Follow below steps and that would be it all,
- Copy ‘Sitecore.Support.391039.dll’ assembly to the ‘\bin’ folder.
- Copy ‘Sitecore.Support.391039.config’ file to the ‘\App_Config\Include’ folder.
- Update all the Solr index configuration files (for each Solr index):
<configuration type="Sitecore.ContentSearch.ContentSearchConfiguration, Sitecore.ContentSearch"> <indexes hint="list:AddIndex"> . . . <index id="<index_name>" type="Sitecore.Support.ContentSearch.SolrProvider.SolrSearchIndex, Sitecore.Support.391039">
You will still need to work upon bringing up the SOLR server. This is how this fix works, it checks if Solr is up on Sitecore start. If no, it skips indexes initializing. However, it may lead to exceptions in log files and inconsistencies while working with Sitecore when Solr is down.
Also, there is an agent defined in the ‘Sitecore.Support.391039.config’ that checks and logs the status of Solr connection every minute (interval value should be changed if needed).
If the Solr connection is restored — indexes will be initialized, the corresponding message will be logged and the search and indexing related functionality will work fine.