Varun Thacker created SOLR-12944: ------------------------------------ Summary: Bugs around createNodeSet=EMPTY Key: SOLR-12944 URL: https://issues.apache.org/jira/browse/SOLR-12944 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Reporter: Varun Thacker
Firstly, As of today we cannot create an empty collection from SolrJ I have a two node cluster and this API call fails with an error {code:java} //Create a coreless collection of 3 shards CollectionAdminRequest.Create create = CollectionAdminRequest .createCollection("test_collection", "conf1", 3, 0) .setCreateNodeSet(OverseerCollectionMessageHandler.CREATE_NODE_SET_EMPTY) .setMaxShardsPerNode(-1);{code} Secondly if I use the API directly , {{[http://localhost:8983/solr/admin/collections?action=create&name=test_coll&numShards=5&createNodeSet=EMPTY] }}the state.json has replicationFactor = nrtReplicas = 1 instead of 0 {code:java} "test_coll":{ "pullReplicas":"0", "replicationFactor":"1", "router":{"name":"compositeId"}, "maxShardsPerNode":"1", "autoAddReplicas":"false", "nrtReplicas":"1", "tlogReplicas":"0", "shards":{ "shard1":{ "range":"80000000-b332ffff", "state":"active", "replicas":{}}, "shard2":{{code} On a side note , I think we should rethink how replicationFactor/nrtReplicas/tlogReplicas/pullReplicas are stored. These values could be stored at a per shard level such that adding a replica will actually refelct the total replication count -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org