Glad that worked. No, there's no way to hard-code as the old solr.xml,
that's pretty antithetical to SolrCloud.
IIRC, though, you're making it too complicated ;)
Machine N goes down that hosts collection_shard1_replica32
Bring machine N+1 up with Solr
Collections API:
ADDREPLCIA with the
Thanks Erick.
createNodeSet works perfect. A nice way of allocating collections among
nodes. When I went through the docs, host tag just noticed so thought to
make use of it, however createNodeSet works just fine for me; and
createNodeSet.shuffle too.
Just wanted to know one more thing. Is there
Wait, rule-based placement isn't what I was talking about at all. You
don't need to knock yourself out understanding the rule based replica
placement, which is being replaced by "Policies" in 7x anyway.
You can just use createNodeSet in the collection CREATE command. It's
a list of nodes (as in
Thanks Erick. I went through the doc
https://lucidworks.com/2015/05/12/rule-based-replica-assignment-solrcloud/
and it helped on how to use "host" tag. However can I use two values to
same key.?
I can do host:!1.1.1.1 but can I do something like host:!1.1.1.1,!2.2.2.2
or
Take a look at the collections API CREATE command, especially the
"createNodeSet". One variant lets you specify the nodes used to
distribute the collection with limited control over what core goes
where through the createNodeSet.shuffle parameter.
Alternatively you can use "EMPTY" for the
Hi,
I just wanted to delegate specific Solr nodes to specific collections. As
per my understanding, when a collection creates in Solr7, core is
automatically creates in the backend. Since my cores are getting different
volume of traffic, I wanted to delegate specific collections to specific
