Steven Bower created SOLR-6877:
----------------------------------
Summary: Order of createNodeList should be respected during
collection creation
Key: SOLR-6877
URL: https://issues.apache.org/jira/browse/SOLR-6877
Project: Solr
Issue Type: Bug
Affects Versions: 4.10.2
Reporter: Steven Bower
When you use the collection api to create a new collection and you specify the
"createNodeList" attribute to the CREATE command it does not preserve the
ordering of the node list and thus does not produce a predictable pattern.
Use case: I want to create a collection with 12 shards (maxShardsPerNode == 4
and I have 3 servers and I specify createNodeList=server1,server2,server3..
I'd expect to get:
server1 : shard1,shard4,shard7,shard10
server2 : shard2,shard5,shard8,shard11
server3 : shard3,shard6,shard9,shard12
But what you often get is something not that because the list order isn't
respected so you might get:
server1 : shard1,shard4,shard7,shard10
server2 : shard3,shard6,shard9,shard12
server3 : shard2,shard5,shard8,shard11
Anyway.. Easy to fix.. patch attached..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
