Wups - sorry folks, I send this prematurely. After typing this out I think I have it figured out - although SPLITSHARD ignores maxShardsPerNode, ADDREPLICA does not. So ADDREPLICA fails because I already have too many shards on a single node.
On Wed, Apr 8, 2015 at 11:18 PM, Ian Rose <ianr...@fullstory.com> wrote: > On my local machine I have the following test setup: > > * 2 "nodes" (JVMs) > * 1 collection named "testdrive", that was originally created with > numShards=1 and maxShardsPerNode=1. > * After a series of SPLITSHARD commands, I now have 4 shards, as follows: > > testdrive_shard1_0_0_replica1 (L) Active 115 > testdrive_shard1_0_1_replica1 (L) Active 0 > testdrive_shard1_1_0_replica1 (L) Active 5 > testdrive_shard1_1_1_replica1 (L) Active 88 > > The number in the last column is the number of documents. The 4 shards > are all on the same node; the second node holds nothing for this collection. > > Already, this situation is a little strange because I have 4 shards on one > node, despite the fact that maxShardsPerNode is 1. My guess is that > SPLITSHARD ignores the maxShardsPerNode value - is that right? > > Now, if I issue an ADDREPLICA command > with collection=testdrive&shard=shard1_0_0, I get the following error: > > "Cannot create shards testdrive. Value of maxShardsPerNode is 1, and the > number of live nodes is 2. This allows a maximum of 2 to be created. Value > of numShards is 4 and value of replicationFactor is 1. This requires 4 > shards to be created (higher than the allowed number)" > > I don't totally understand this. > > >
