A SearchStax Managed Search service client reported a mysterious “could not restore core” error.
ERROR (OverseerThreadFactory-315-thread-451-processing-n:10.35.26.134:8983_solr) [c:sitecore_sxa_web_index_secondary ] o.a.s.c.a.c.OverseerCollectionMessageHandler Collection: sitecore_sxa_web_index_secondary operation: restore failed:org.apache.solr.common.SolrException: "Could not restore core"]
The critical fragment was “Could not restore core.”
SearchStax engineers determined that the client was trying to implement a “blue-green deployment” by copying live index files from one collection to another on the same deployment. Index files are highly dynamic. Copying them while they are updating makes index corruption almost certain. Solr could not construct a new core from the copied files.
See Nodes Use Different Disk Space for some insight into Solr index segment files.
Please see Solr Blue-Green Architecture for insights on implementing a blue-green architecture using Managed Search.
Questions?
Do not hesitate to contact the SearchStax Support Desk.