While using MiniSolrCloudCluster on another project with a solr.xml that
looks like the standard solr.xml, I ran into some problems.
The default solr.xml has a solrCloud element with these elements:
<str name="host">${host:}</str>
<int name="hostPort">${jetty.port:8983}</int>
<str name="hostContext">${hostContext:solr}</str>
And MiniSolrCloudCluster.DEFAULT_CLOUD_SOLR_XML, a string literal, has the
equivalent of this:
<str name="host">127.0.0.1</str>
<int name="hostPort">${hostPort:8983}</int>
<str name="hostContext">${hostContext:solr}</str>
Notice the system property for the <hostPort> element is either
"jetty.port" or "hostPort". *I submit that the system properties used here
ought to be consistent.* So for example do away with jetty.port in lieu of
hostPort given what appears more natural and consistent here. This
"hostPort" System property is used in a bunch of places in tests. I've
also seen a jetty.host lingering somewhere in some jetty xml files.
Also notice that the default solr.xml "host" has an empty string default,
and AFAICT this is not equivalent to 127.0.0.1.
Any thoughts on this from folks in terms of understanding if/why we can't
do this, or why this inconsistency is this way today?
Two relevant issues:
https://issues.apache.org/jira/browse/SOLR-2722 (Mark Miller, Hossman
https://issues.apache.org/jira/browse/SOLR-7976 (Shalin)
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
