Guillaume Jactat created SOLR-17219:
---------------------------------------
Summary: Exceptions occur while Solr reads some core's configset
(java.io.IOException: Error opening /configs/<path to file>)
Key: SOLR-17219
URL: https://issues.apache.org/jira/browse/SOLR-17219
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Affects Versions: 9.5.0
Environment: My first attempts were on Windows via services hosted
through procrun (both zookeeper and solr nodes). I also tried with a Docker
Dekstop ensemble.
It seems that this error occurs less frequently via Docker. But it happens
anyway.
Reporter: Guillaume Jactat
Attachments: stack.txt
Hello,
I'm currently testing SolrCloud to get a better idea of how to recover from
node failures.
I have a simple configuration: one ZooKeeper server and 3 Solr nodes.
I upload a configset in Zookeeper via Solr's Configsets API. I create 200
collections, all bound to the same configset.
I leave the collections empty for the moment.
When I stop/start one node, the process of recovery happens. And almost
everytime, i get the following error (full stack is attached to this issue):
java.io.IOException: Error opening
/configs/CoreModel–CB38FE6CFE/lang/stopwords_fi.txt
Its not always the same configset's file. Sometimes, everything goes fine. But
when this error occurs, the whole process of recovery seem compromised, leaving
a lot of cores/collections "down". No "retry" happens, maybe because Solr
assumes that the configset is wrong and no retry could fix it ?
I've tried the same setup on Windows Service (procrun) and Docker Desktop
containers. It seems that this error occurs less frequently with docker but it
happens anyway.
I didn't find anything close to this error on the web... I have no clue why
this error happens.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
