Symptom
- During a full solr indexing job, the process fails with the message: "Could not export configuration for index"
- Logs may also show: "Could not reload configuration for index"
- solr cluster was health during that time, no cpu, memory resource issue, no restart.
- The failure occurs while exporting the index configuration as part of the indexing initialization without any detail error message like "Could not reload configuration for index: name=master_tciusa_Product_flop","name":"de.hybris.platform.solrfacetsearch.solr.exceptions.SolrServiceException","cause":{"commonElementCount":15,"localizedMessage":"Timeout while waiting for async request: requestId=3da3f4f8-4d41-49a8-8091-9e40ecbb08b5, timeout=300,000" or "Could not export configuration for index: name=master_tciindia_Product_default","name":"de.hybris.platform.solrfacetsearch.solr.exceptions.SolrServiceException","cause":{"commonElementCount":15,"localizedMessage":"Could not find a healthy node to handle the request.","message":"Could not find a healthy node to handle the request."
Read more...
Environment
- Product: SAP Commerce Cloud
- solr cloud and solr 9.x
Product
SAP Commerce Cloud all versions
Keywords
solr indexing, could not export configuration, could not reload configuration, full index failure, configuration reload, jvm heap, insufficient memory, solr heap, scale factor, solrfacetsearch, indexer job, rolling restart, schema load, cache warmup , 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.
SAP Knowledge Base Article - Preview