SAP Knowledge Base Article - Preview

3602273 - Error: SolrException: RELOAD timed out after 180000 ms, causing Solr Index Failure

Symptom

When triggering a solr index job in the Backoffice, the index job fails immediately. Check in the backend / OpenSearch, and can find the error message below:

Error during indexer call: {IndexName}. Aborting Cronjob {CronjobName}. Reason: de.hybris.platform.solrfacetsearch.solr.exceptions.SolrServiceException: Could not export configuration for index: name={CollectionName}.
ERROR (xxx-solr-0.solr.default.svc.cluster.local-x) [c:collection_name: r: x: t:solr-0.solr.default.svc.cluster.local-x] o.a.s.s.HttpSolrCall 500 Exception => org.apache.solr.common.SolrException: RELOAD timed out after 180000ms at org.apache.solr.cloud.api.collections.DistributedCollectionConfigSetCommandRunner.runCollectionCommand(DistributedCollectionConfigSetCommandRunner.java:304)

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

  • SAP Commerce Cloud
  • SAP Commerce

Product

SAP Commerce Cloud all versions

Keywords

Indexing, Shard, TWO_PHASE, Direct, SolrServiceException, IndexerException, batch size, inactive, replication, ZooKeeper, runCollectionCommand, DEFAULT_COLLECTION_OP_TIMEOUT, synchronous , KBA , CEC-SCC-COM-SRC-SER , Search and Navigation , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.