[jira] [Resolved] (SOLR-6506) SolrCloud route.name=implicit not effect

["Cassandra Targett (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett resolved SOLR-6506.
-------------------------------------
    Resolution: Cannot Reproduce

I suspect the more modern approach of starting Solr with bin/solr renders this somewhat obsolete in terms of how startup params are passed. Also, I think we would in general recommend that the Collections API be used to set these params instead of setting them as system params at startup.

> SolrCloud   route.name=implicit  not effect
> -------------------------------------------
>
>                 Key: SOLR-6506
>                 URL: https://issues.apache.org/jira/browse/SOLR-6506
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.9
>            Reporter: Smart  Zhang
>
>  The first node i start with 
> "java -Xms512m -Xmx1536m -DzkRun -Djetty.port=8983 -Dshards=shard1,shard2,shard3 -Droute.name=implicit
> -Dsolr.data.dir=/data/data1 -Dsolr.solr.home=multicore -Dbootstrap_conf=true -DzkHost=localhost:2182 -jar start.jar "
> I want to start up the second node to shard2, but it defaut belong to shard1, the second node command is
> "java -Xms512m -Xmx1536m -Djetty.port=8988 -Dsolr.data.dir=/data/data6 -Dsolr.solr.home=multicore -DzkHost=localhost:2182 -jar start.jar"
>  I use  "http://ip:port/solr/admin/collections?action=CREATESHARD&shard=shard2&collection=mycol"  to create a new shard also does not effect. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org