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 2014/12/22 18:35:13 UTC
[jira] [Commented] (SOLR-6877) Order of createNodeList should be
respected during collection creation
[ https://issues.apache.org/jira/browse/SOLR-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255962#comment-14255962 ]
Erick Erickson commented on SOLR-6877:
--------------------------------------
OK, I'll wait for SOLR-6729 to get a patch before looking any more.
> 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
> Assignee: Erick Erickson
> Attachments: SOLR-6877.patch
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org