Many Sitecore sites depend on search far more than people realize. Site search is the obvious part, but listing pages, related articles, product filters and even some navigation are often powered by Solr indexes behind the scenes. When the index is wrong, pages look empty or out of date, and editors assume publishing is broken.
How Sitecore uses Solr, briefly
Sitecore keeps a copy of item content in Solr so it can search it quickly. The main indexes are sitecore_master_index (content being edited), sitecore_web_index (published content) and sitecore_core_index. When content changes, an index update strategy decides when Solr gets updated. If that step fails or doesn't run, Solr and the database drift apart.
Start here: three quick checks
- Read the Crawling log. Sitecore writes indexing activity and errors to
Crawling.log.*.txtin the data folder. Errors there usually point straight at the cause. - Compare document counts. In the Solr admin UI, open the core and check the number of documents. If it's far lower than expected, or zero, the index is incomplete.
- Check Solr itself. Look at the Solr logging page and the JVM memory on the Solr dashboard. A Solr server that's out of memory causes slow queries and failed updates.
1. The wrong index update strategy
Each index has one or more update strategies in its configuration. The common ones are:
onPublishEndAsync: updates the web index after each publish. This is the normal choice forsitecore_web_index.syncMaster: updates the master index immediately on every save. Simple, but it can slow down editing on busy authoring servers.intervalAsyncMaster: updates the master index in batches on a timer, which is lighter on authoring.manual: never updates automatically. If a custom index is set to manual by mistake, it goes stale quietly.
Fix: check the strategies in /sitecore/admin/showconfig.aspx on each server role. Custom indexes copied from examples often have the wrong strategy, or a strategy that only runs on the content management server.
2. The Solr schema wasn't updated
When developers add new fields, computed fields or languages, Solr may need schema updates. If the schema doesn't know a field type, documents fail to index, often with errors like "unknown field" in the Crawling log.
Fix: in Sitecore 9 and later, use Control Panel > Indexing > Populate Solr Managed Schema for the affected indexes, then rebuild them. Make this part of your deployment checklist so it isn't forgotten after releases.
3. Rebuilds that take hours or never finish
A full rebuild reads every item in scope and sends it to Solr. On large sites, slow computed fields make this crawl. A computed field that reads other items, calls an external service or loads media can turn a 20-minute rebuild into an overnight job. If an app pool recycle happens during the rebuild, the rebuild stops.
Fix:
- Review custom computed fields and remove expensive work from them.
- Narrow each index to the parts of the tree and templates it actually needs.
- Run rebuilds in a quiet window, and check that app pool recycling won't interrupt them.
- For the web index on production, use
SwitchOnRebuildSolrSearchIndex. It rebuilds into a second core and switches over when finished, so the live site keeps working during the rebuild.
4. Solr is short of memory or disk
Solr runs on Java, and the default heap size is often too small for production. When it runs short of memory, queries slow down, updates time out and Solr may restart. Running out of disk space during a rebuild also leaves cores broken.
Fix: set the Solr heap size to suit your index sizes, leave enough free memory on the server for the operating system's file cache, and monitor disk space. Solr should usually run on its own server, or SolrCloud for larger setups, not on the same machine as Sitecore.
5. Solr version mismatches
Each Sitecore version supports specific Solr versions. Running a newer or older Solr than supported can cause odd errors that are hard to trace. This often happens after an infrastructure team upgrades Solr on its own, or after a Sitecore upgrade where Solr was left behind.
Fix: check the Solr compatibility table for your exact Sitecore version and make sure Solr matches before you start debugging anything else.
6. Changes are indexed but not visible yet
Solr doesn't make new documents searchable instantly. It does that on a "commit". If commit settings are very long, new content appears in Solr minutes later than expected, which looks like a Sitecore bug.
Fix: review the autoCommit and autoSoftCommit settings in the core's solrconfig.xml. A soft commit every few seconds is common for content sites.
What to do next
Begin with the Crawling log and the document counts. Together they tell you whether the problem is in Sitecore, in Solr, or in between. If search problems keep coming back after each release, the fix is usually a mix of configuration cleanup and a better deployment checklist, which I can help with through a support engagement.
