[jira] [Commented] (SOLR-7716) misleading errors reported for CREATESHARD if new shard would exceed maxShardsPerNode

["Erick Erickson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-7716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598009#comment-14598009 ] 

Erick Erickson commented on SOLR-7716:
--------------------------------------

SOLR-5128 mentions allowing parameters like maxShardsPerNode to be changed after collection creation.

> misleading errors reported for CREATESHARD if new shard would exceed maxShardsPerNode
> -------------------------------------------------------------------------------------
>
>                 Key: SOLR-7716
>                 URL: https://issues.apache.org/jira/browse/SOLR-7716
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: Trunk, 5x
>            Reporter: Erick Erickson
>            Priority: Minor
>
> If I create a collection with implicit routing and, say, maxShardsPerNode=3, then start creating shards, when I create the 4th shard I get an error. So far so good. The error is very misleading though, see below.
> Saw this on a degenerate case of a single Solr instance, not sure if you get the same error on a multi-node cluster.
> <str name="Operation createshard caused exception:">
> ...... Cannot create collection eoe. No live Solr-instances
> </str>
> <lst name="exception">
> <str name="msg">Cannot create collection eoe. No live Solr-instances</str>
> <int name="rspCode">400</int>
> .
> .
> .
> Related question is I don't think there's a graceful way to increase maxShardsPerNode after the collection is created.



--
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