On 1/28/2016 12:15 AM, Pranaya Behera wrote:
> I have checked in the admin UI and now I have created 3 shards 2
> replicas for each shard and 1 shard per node. This is what I get:
>
> {"card":{ "replicationFactor":"2", "router":{"name":"compositeId"},
> "maxShardsPerNode":"1", "autoAddReplicas":"false", "shards":{
> "shard1":{ "range":"80000000-d554ffff", "state":"active",
> "replicas":{}}, "shard2":{ "range":"d5550000-2aa9ffff",
> "state":"active", "replicas":{}}, "shard3":{
> "range":"2aaa0000-7fffffff", "state":"active", "replicas":{}}}}} There
> is no replica. How is this possible? This is what I used to create the
> collection: curl
> "http://localhost:8983/solr/admin/collections?action=CREATE&name=card&numShards=3&replicationFactor=2&maxShardsPerNode=1&createNodeSet=localhost:8983_solr,localhost:8984_solr,localhost:8985_solr&createNodeSet.shuffle=true&collection.configName=igp";
>
With numShards=3 and replicationFactor=2, Solr will need to create six
cores to satisfy the CREATE. With the further restrictions of
maxShardsPerNode=1 and a list of three nodes to use, this request is
impossible to fulfill.
If this request appears to succeed but does not create a usable
clusterstate, then there may be a bug in the detection of impossible
CREATE requests. The request *should* have failed entirely, because it
is not possible.
I noticed that the parameters in the first message on this thread
indicated maxShardsPerNode=2, so *that* request should have worked
correctly.
For each test that you are trying, you need to include what you tried,
what you expected, and what actually happened. The info about what
actually happened needs to be non-ambiguous. Screenshots and actual log
entries are a good way to make sure the information is concrete and
accurate. Don't send these things as attachments -- put them on
appropriate sharing sites (gist, dropbox, etc.) and include URLs.
https://wiki.apache.org/solr/UsingMailingLists
Thanks,
Shawn
