SOLR-4321: Collections API will sometimes use a node more than once, even when more unused nodes are available.
Fixed for 4.2. I'm going to try and drive a 4.2 release starting next week. - Mark On Mar 4, 2013, at 7:05 AM, adfel70 <adfe...@gmail.com> wrote: > I'm using solr 4.1 > . > I have a cluster with 30 nodes, I use collections API's create command to > create a collection of 5 shards and 2 replicas. > I get a collection that is built on 6 nodes out of the 30, with multiple > shards using the same nodes. > There is nothing wrong with this, but as I have 30 nodes, I expect the > collection to distribute among more nodes. > > Note that I tried deleting the collection and creating it again, and always > have the same "problem" (with different nodes, of course). > > Any idea how to achieve this without manually adding cores on the nodes that > I choose? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/how-does-collections-API-choose-nodes-for-CREATE-command-tp4044529.html > Sent from the Solr - User mailing list archive at Nabble.com.
