Hi
Before upgrading to Solr 4.0.0 we used to handle our collection creation
ourselves, by creating each shards through the low-level CoreAdmin API.
We used to create multiple shards under the same collection on each Solr
server. Performance tests has shown that this is a good idea, and it is
also a good idea for easy elasticity later on - it is much easier to
move an entire existing shards from one Solr server to another one that
just joined the cluter than it is to split an exsiting shard among the
Solr that used to run it and the new Solr.
Now we are trying to migrate to the Solr Collection API for creation of
collections, but it seems like it will not accept multiple shards under
the same collection running on the same Solr server. E.g. if we have 4
Solr servers and ask to have a collection created with 8 shards, all 8
shards will be "created" but only 4 of them will acutally run - one on
each Solr server.
Is the a good reason why Solr does not allow multiple shards under the
same collection to run on the same Solr server, or is it just made this
way "by coincidence"? In general I seek info on the matter - is it
planed for later? etc.
Thanks!
Regards, Per Steffensen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
