I noticed that Shawn mentioned (
https://issues.apache.org/jira/browse/SOLR-4732) that “when you rename or
swap cores, the solr.core.name property does NOT get updated until you
restart Solr”. I’m wondering if there’s any way possible to update this
property other than restarting the entire Solr application. I’m currently
using Solr 4.3.0.
My original thought was that I may be able to update this property by
issuing a core RELOAD after the SWAP, which would mean that Solr is at
least responding to search requests while it’s reloading the core. Would
this work?
I’m trying to avoid restarting the entirety of Solr, as I have over 100
cores, and the startup time can be a minute or two. Additionally, I’m
attempting to share the same schema/configuration among these 100 cores,
which I why I’m using the ${solr.core.name} property for replication and
the data import handler, so that I only need one copy of these files.
I’d imagine that similar issues may be encountered while implementing
https://issues.apache.org/jira/browse/SOLR-4478, since this intends to
share config sets across multiple cores. I would think that the core name
may be an important property to use in the config set scenario.
Thanks!
