You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2015/06/23 19:30:06 UTC

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

Erick Erickson created SOLR-7716:
------------------------------------

             Summary: 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: 5x, Trunk
            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