Skip to main content

Sitecore Solr/SearchStax Auto Suggestions - suggester was not built error and fix

HI Team,

This one will be very quick blog post, But sharing it here so it helps anyone on the internet having same issue

Problem

We are using SearchStax and we have been using auto suggestions functionality of it, Everything was working fine and suddenly lot of users started reporting that they are not able to search anything in the search box.

As this was P1, I started looking into the probable cause and logs, first i saw in console that we were getting 500 error, that means there is some issue being thrown from the backend.

Upon checking logs found following in logs 



The error was "suggester was not built"

Well, I knew there is some issue with suggester which causing it to fail, but puzzle was, It has always been working for us

Now, because we have this error on SearchStax documentation, If you refer below link, it says 

https://www.searchstax.com/docs/hc/suggester-was-not-built/

"The root cause is often query fields that are not defined in the Solr schema. Look in the solr.log files for index errors; fix the queries; update the schema; reload the indexes; and restart the suggester. The solution is likely to be along that path."

Well, I could confirm that there was no change with schema and on DEV / UAT it was working just fine

Solution

Before creating a support ticket with SearchStax, i wanted to spend sometime understanding it and looking into the logs in details, i got below URL which was getting fired while someone uses auto suggestion search box, and this URL was giving the error

https://<<solr cloud url>>/solr/sitecore_web_index/suggest?q=test+u&rows=100000000&fq=_indexname%3a(sitecore_web_index)&suggest=true&suggest.count=10&suggest.build=false&version=2.2&wt=xml

I read more about suggest.build and how suggester component is working, so if you refer below link 

https://doc.sitecore.com/xp/en/developers/103/platform-administration-and-architecture/using-solr-auto-suggest.html


Well, i just tried changing that flag to true in above URL and hit it in the browser, Before this, i never did anything like this, it's new for me too, but well it started working and it was able to built the suggester and live site started showing the results just fine 


Though i was able to resolve it, Just to double check this approach and as it was P1 and also to know why it stopped working? I created a ticket with SearchStax for this behavior, Awaiting for their reply & will update this space once i get something around it.

Labels:

Comments

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...
3 comments
Read more

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...
Post a Comment
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more