On 12/23/2013 08:42 PM, Shawn Heisey wrote:
On 12/23/2013 12:23 PM, David Santamauro wrote:
I managed to create 8 new cores and the Solr Admin cloud page showed
them wonderfully as active replicas.
The only issue I have is what goes into solr.xml (I'm using tomcat)?
Putting
<core name="..." />
for each of the new cores I created seemed like the reasonable approach
but when I tested a tomcat restart, the distribution was messed up ...
for one thing, the cores on the new machine showed up as collections!
And tomcat never even made it to accept connections for some reason.
I cleaned everything up with zookepper so my graph looks like it should
and I removed that new machine from the distribution (by removing zk
attributes) and restarted .. all is well again.
Any idea what could have went wrong on tomcat restart?
You may have one or more of the SolrCloud 'bootstrap' options on the
startup commandline. The bootstrap options are intended to be used
once, in order to bootstrap from a non-SolrCloud setup to a SolrCloud setup.
No, no unnecessary options. I manually bootstrapped a common config.
Between the Collections API and the CoreAdmin API, you should never need
to edit solr.xml (if using the pre-4.4 format) or core.properties files
(if using core discovery, available 4.4 and later) directly.
Now this I don't understand. If I have created cores through the
CoreAdmin API, how is solr.xml affected? If I don't edit it, how does
SOLR know what cores it has to expose to a distributed collection?
thanks
David
