When using Collections API CREATE action, I found that sometimes default shard placement is correct (leader and replica on different servers) and sometimes not. So I was looking for a simple and reliable way to ensure better placement. It seems like I will have to do it manually for best control, as recommended by Erick and you.
Thanks, Isabelle PS: I deleted emails from thread history, because my reply keeps being rejected by apache server as spam... On Thu, Nov 6, 2014 at 8:13 AM, ralph tice <ralph.t...@gmail.com> wrote: > I've had a bad enough experience with the default shard placement that I > create a collection with one shard, add the shards where I want them, then > use add/delete replica to move the first one to the right machine/port. > > Typically this is in a SolrCloud of dozens or hundreds of shards. Our > shards are all partitioned by time so there are big performance advantages > to optimal placement across JVMs and machines. > > What sort of situation do you not have trouble with default shard > placement? > > > On Wed, Nov 5, 2014 at 5:10 PM, Erick Erickson <erickerick...@gmail.com> > wrote: > > They should be pretty well distributed by default, but if you want to > > take manual control, you can use the createNodeSet param on CREATE > > (with replication factor of 1) and then ADDREPLICA with the node param > > to put replicas for shards exactly where you want. > > > > Best, > > Erick > > > >
