You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Timothy Potter (JIRA)" <ji...@apache.org> on 2014/09/05 18:51:29 UTC

[jira] [Resolved] (SOLR-6447) bin/solr -c doesn't set numShards for collection1

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

Timothy Potter resolved SOLR-6447.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.11
                   5.0

> bin/solr -c doesn't set numShards for collection1
> -------------------------------------------------
>
>                 Key: SOLR-6447
>                 URL: https://issues.apache.org/jira/browse/SOLR-6447
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0, 4.10
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>             Fix For: 5.0, 4.11
>
>
> bin/solr -c will start Solr in cloud mode. Since collection1 includes a core.properties, it will be auto-discovered and created into a collection. So the script uses:
> -Dbootstrap_confdir=./solr/collection1/conf -Dcollection.configName=myconf
> However, it's not setting -DnumShards for collection1, which results in collection1 being created using the implicit router and a null range. While we have this collection1 being auto-deployed, the script should set numShards as well so that collection1 is created correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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