Thanks for your responses.
I’ve tried to get more familiar with the Autoscaling API. I’ve applied a
nodeAdded trigger but I’m stuck trying to think of a cluster policy that would
suit my scenario; something like “All new nodes need must have one replica from
each available collection”
Is this
Ah hmm I guess I didn't realize the autoscaling didn't use the rule based
stuff (haven't had opportunity to work with either). If it's deprecated,
maybe that suggests we need a highly visible warning box on the ref guide
page?
On Thu, Jul 5, 2018 at 12:18 AM, Shalin Shekhar Mangar <
The rule based replica placement was deprecated. The autoscaling APIs are
the way to go. Please see
http://lucene.apache.org/solr/guide/7_3/solrcloud-autoscaling.html
Your use-case is interesting. By default, the trigger for nodeAdded event
will move replicas from the most loaded nodes to the new
Perhaps the rule based replica placement stuff would do the trick?
https://lucene.apache.org/solr/guide/7_3/rule-based-replica-placement.html
I haven't used it myself but I've seen lots of work going into it lately...
On Wed, Jul 4, 2018 at 12:35 PM, Duncan, Adam
wrote:
> Hi all,
>
> Our team
Hi all,
Our team use Solrcloud for Solr 5.1 and are investigating an upgrade to 7.3
Currently we have a working scale-up approach for adding a new server to the
cluster beyond the initial collection creation.
We’ve automated the install of Solr on new servers and, following that, we
register
