[
https://issues.apache.org/jira/browse/SOLR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582789#comment-13582789
]
Mark Miller commented on SOLR-4450:
-----------------------------------
bq Another possibility, which might work better in a "do everything the same"
environment - start up initially with no config sets, no cores, no bootstrap
options then use the zkcli script included with Solr to load configs.
Right. And we have a few options here regarding config - we should continue
improving the zkcli tool to make it very easy to pop up a config folder for a
collection (it's not bad now, but could be polished), and we should continue on
the issues that make it easy to post new config files to a collection. That
would also give you the option of starting a new collection with whatever
random default minimal config, and then you could just post a new schema.xml,
then solrconfig.xml when you have the schema right, etc. We also have issues
around specifying a configuration files when you use the collections create
API.
I think we already have a lot of momentum towards making a lot of this simpler,
it just requires some work from people to finish it off.
> Developer Curb Appeal: Need consistent command line arguments for all nodes
> ---------------------------------------------------------------------------
>
> Key: SOLR-4450
> URL: https://issues.apache.org/jira/browse/SOLR-4450
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Mark Bennett
> Fix For: 4.2
>
>
> Suppose you want to create a small 4 node cluster (2x2, two shards, each
> replicated), each on it's own machine.
> It'd be nice to use the same script in /etc/init.d to start them all, but
> it's hard to come up with a set of arguments that works for both the first
> and subsequent nodes.
> When MANUALLY starting them, the arguments for the first node are different
> than for subsequent nodes:
> Node A like this:
> -DzkRun -DnumShards=2 -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=MyConfig -jar start.jar
> Vs. the other 3 nodes, B, C, D:
> -DzkHost=nodeA:9983 -jar start.jar
> But if you combine them, you either still have to rely on Node A being up
> first, and have all nodes reference it:
> -DzkRun -DzkHost=nodeA:9983 -DnumShards=2
> -Dbootstrap_confdir=./solr/collection1/conf -Dcollection.configName=MyConfig
> OR you can try to specify the address of all 4 machines, in all 4 startup
> scripts, which seems logical but doesn't work:
> -DzkRun -DzkHost=nodeA:9983,nodeB:9983,nodeC:9983,nodeD:9983
> -DnumShards=2 -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=MyConfig
> This gives an error:
> org.apache.solr.common.SolrException log
> SEVERE: null:java.lang.IllegalArgumentException: port out of range:-1
> This thread suggests a possible change in syntax, but doesn't seem to work
> (at least with the embedded ZooKeeper)
> Thread:
> http://lucene.472066.n3.nabble.com/solr4-0-problem-zkHost-with-multiple-hosts-throws-out-of-range-exception-td4014440.html
> Syntax:
> -DzkRun -DzkHost=nodeA:9983,nodeB:9983,nodeC:9983,nodeD:9983/solrroot
> -DnumShards=2 -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=MyConfig
> Error:
> SEVERE: Could not start Solr. Check solr/home property and the logs
> Feb 12, 2013 1:36:49 PM org.apache.solr.common.SolrException log
> SEVERE: null:java.lang.NumberFormatException: For input string:
> "9983/solrroot"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> So:
> * There needs to be some syntax that all nodes can run, even if it requires
> listing addresses (or multicast!)
> * And then clear documentation about suggesting external ZooKeeper to be used
> for production (list being maintained in SOLR-4444)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
