"2022-10-11 15:42:34 ERROR HttpSolrCall: - org.apache.solr.common.SolrException: java.io.FileNotFoundException: /usr/share/solr/example/multicore/INDEX_NAME/data/tlog/tlog.0000000000000002357 (No such file or directory)"
(replace INDEX_NAME with your own Opensolr INDEX NAME)
That's all because you are using updateLog in your solrconfig.xml
You can generally fix this by clicking Reload/Repair under the tools menu in your Opensolr index control panel.
The logic is that updateLog uses up a lot of system resources and causes the index to be corrupted until the tlog files are being removed, which is what that Reload/Repair button does among other things.
Another more permanent fix (only if you really must use updateLog in solrconfig.xml) is to move over to a larger dedicated OpenSolr Cloud server in which all server resources are not shared, and this issue will be mitigated.
Also, if you go here:
And you select solrconfig.xml form that select drop-down box, you then look for the updateLog snippet, and remove that tag entirely, for example:
Then this issue will not show up until you upload the config files from Drupal again. At which time you will have to do this again, or tell Drupal not to add that somehow.
You can use that, since that will try to reset the tlog (updateLog) of the Solr Index, which that's the thing that gets corrupted, and should sort this out.