Sitecore Docs - Tech Tips by GS

 The Problem We use SOLRcloud for SOLR with Zookeeper. While performing my routine development activities, I encountered that my local SOLR instance is giving a weird error as shown in snapshot below -  The Solution We checked SOLR logs and could see error like below repeating continuously -  2024-11-10 22:31:31.216 ERROR (zkConnectionManagerCallback-7-thread-1-EventThread) [   ] o.a.s.c.LeaderElector node exists => org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /overseer_elect/leader at org.apache.zookeeper.KeeperException.create(KeeperException.java:126) org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /overseer_elect/leader at org.apache.zookeeper.KeeperException.create(KeeperException.java:126) ~[zookeeper-3.5.5.jar:3.5.5] at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) ~[zookeeper-3.5.5.jar:3.5.5] at org.apache.zookeeper.ZooKeeper.create(...

 The Problem I was working on Sitecore installation on a new machine. Everything was running smooth but the SOLR service always ended up in PAUSED state.  The Research I tried stopping the service and then starting it using NSSM multiple times but it did not help. Then I thought of removing and recreating the service but again no help. And then it was followed by a machine restart and the service still ended up in PAUSED state.  I started googling about this issue and found answers suggesting that may be JAVA_HOME environment variable is not set or may be JAVA is not installed. I opened my command prompt to execute  echo %java_home% to get value for JAVA_HOME environment variable and it returned a blank value. This proved there is definitely an issue with JAVA setup on my new machine. Next,  I executed  java -version in cmd prompt and I found that the new machine is using Microsoft build of openJDK   instead of JRE (snapshot below) It was fou...

The Problem While working on Sitecore, it may happen that one of your SSL certificates may expire after some time. This can cause functionalities to break.  For e.g., I encountered a problem where the SOLR search functionalities on my local Sitecore instance stopped working. You may be having similar problem if you face following issues -  when you search a GUID in Content Editor to locate an item, it would not return any result and say that an exception has occurred.  when you try to rebuild my SOLR indexes using Rebuild Search Indexes in Control Panel, the dialog did not list any of my SOLR indexes. The Research I looked into the logs to find the root cause to the problem and found following warnings -  128216 15:40:08 WARN  IsOnline: Test connection has failed with an exception. Type: 'SolrConnectionException', Message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.' I tried to load my local SOLR ...

SOLR SEARCH QUICK NOTES http://www.solrtutorial.com/solr-query-syntax.html BASIC CONCEPTS Solr prepares indexes. Indexes contains documents and documents contains fields. Documents can be assumed as rows in a table and fields as columns in tables. Before adding documents to index, we need to specify the schema. (not advisable to change schema after documents have been added).  The schema declares - what kinds of fields there are which field should be used as primary key which fields are required how to index and search each field When we search for a word, the word undergoes transformation to get converted to a token. SOLR then looks for these tokens in its indexes. Each token contains references to pages where it was found when SOLR was crawling and this is how search results are returned. All fields are not searchable. Many of them are maintained in indexes so that when a match is found, the field values may need to be displayed in the search results. This is done by following se...

The Problem Recently, a Sitecore developer reported an issue where he could not get more than 100 values for a facet field in SXA search component. He tried updating Query.MaxItems and also  XA.Foundation.Search.QueryMaxItems but still did not get more that 100 values for the facet field. The Research I started looking into this out of curiosity. I checked Sitecore configs and did not find any other setting which could be affecting it. I realized soon that this was most likely something limited on SOLR side. On researching, I found out that indeed this is related to SOLR default settings. Below is the snapshot from documentation about it and more info can be found here -  The Solution So, on your SOLR Server, edit the solrconfig.xml for the index you are using. It is found in the conf folder of your index. Find the requesthandler you are using, for e.g. "/select", and add <str name="facet.limit">-1</str> as in snapshot below -       Repeat th...

We were using docker based Sitecore 10.1 for local development. This was an upgrade project and I was working on validating the items in upgraded Sitecore 10.1 environment.  Problem I started performing some simple searches in Content Editor's search box but got no results returned even when the item existed in the content tree. I realized I have never built the SOLR indexes since I setup the environment. So I went to control panel and attempted index rebuild. I got the following error -  Job started: Index_Update_IndexName=sitecore_master_index |# Exception : System . Reflection . TargetInvocationException : Exception has been thrown by the target of an invocation. ---> SolrNet . Exceptions . SolrConnectionException : <?xml version="1.0" encoding=" UTF -8"?> <response> <lst name="response Header "> < int name="rf">1< / int > < int name="status">400< / int > < int name=...