Missed the replicationFactor parameter. Works great now.
http://imm.io/RM66
Thanks a lot for you help,
One last question. in terms of scalability, having this design of one
collection per customer, with one shard and many replicas, A query will
be handled by one shard (or replica) on one node only and scalability
here is really about load balancing queries between the replicas only.
i.e no distributed search. is this correct?
Hassan
On 05/01/13 15:47, Per Steffensen wrote:
Do you remember to add replicationFactor parameter when you create
your "customer1" and "customer2" collections/shards?
http://wiki.apache.org/solr/SolrCloud#Managing_collections_via_the_Collections_API
(note that maxShardsPerNode and createNodeSet params are not available
in 4.0.0, but will be in 4.1)
Regards, Per Steffensen
On 1/5/13 11:55 AM, Hassan wrote:
Thanks Per and Otis,
It is much clearer now but I have a question about adding new solr
nodes and collections.
I have a dedicated zookeeper instance. Lets say I have uploaded my
configuration to zookeeper using "zkcli" and named it, say,
"configuration1".
Now I want to create a new solrcloud from scratch with two solr
nodes. I need to create a new collection (with one shard) called
"customer1" using the configuration name "configuration1". I have
tried different ways using Collections API, zkcli
linkconfig/downconfig but I cannot get it to work. Collection is only
available on one node. The example "collection1" works as expected
where one node has the Leader shard and the other node has the
replica. See the cloud graph
http://imageshack.us/f/706/selection008p.png/
What is the correct way to dynamically add collections to already
existing nodes and new nodes?
Thanks you,
Hs
