From the post:
The SolrCloud wiki page gives various examples but left a few things unclear for me. The examples only show Solr instances which host one core/shard, and it doesn’t go deep on the relation between cores, collections and shards, or how to manage configurations.
In this blog, we will have a look at an example where we host multiple shards per instance, and explain some details along the way.
If you have any interest in SolrCloud, this is a post for you. Forward it to your friends if they are interested in Solr. And family. Well, maybe not that last one.
I have a weakness for posts that take the time to call out “…shard and slice are often used in ambiguous ways…,” establish a difference and then use those terms consistently.
One of the primary weaknesses of software projects is that “documentation” is treated with about the same concern as “requirements.”
The problem is that the original programmers may understand ambiguities and if you want a cult program, that’s great. The problem is that to be successful software, that is software that is widely used, it has to be understood by as many programmers as possible. Possibly even users if it is an end use product.
Think of it this way: You don’t want to be distracted from the next great software project by endless questions that you have to stop and answer. Do the documentation along the way and you won’t lose time on the next great project. Which we are all waiting to see. Documentation is a win-win situation.