[
https://issues.apache.org/jira/browse/SOLR-12715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602936#comment-16602936
]
ASF subversion and git services commented on SOLR-12715:
--------------------------------------------------------
Commit cc573d7bb6f5e01d631f40da951c2b4f660e0961 in lucene-solr's branch
refs/heads/branch_7x from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cc573d7 ]
SOLR-12715: NodeAddedTrigger should support adding replicas to new nodes by
setting preferredOperation=addreplica
This commit adds support for preferredOperation configuration parameter which
defaults to movereplica. Changes ComputePlanAction to add all
(collection,shard) pair as hints to AddReplicaSuggester when addreplica is
selected as the preferred operation.
(cherry picked from commit 34a85014d5a09e07ddd48d735a8a96a57e92a44d)
> NodeAddedTrigger should support adding replicas to new nodes
> ------------------------------------------------------------
>
> Key: SOLR-12715
> URL: https://issues.apache.org/jira/browse/SOLR-12715
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-12715.patch, SOLR-12715.patch, SOLR-12715.patch
>
>
> NodeAddedTrigger only moves replicas from other nodes to the newly added
> node(s). We should add support for addreplica operations via
> preferredOperation flag as is done in other triggers like MetricsTrigger and
> ScheduledTrigger.
> The use-case is to add replica(s) of one or more collections to a new node
> automatically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
