[
https://issues.apache.org/jira/browse/SOLR-12715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602777#comment-16602777
]
Shalin Shekhar Mangar commented on SOLR-12715:
----------------------------------------------
Patch:
# Adds {{preferredOperation}} as a property for {{NodeAddedTrigger}}
# The {{ComputePlanAction}} specializes Suggester creation for the trigger if
preferredOperation is addreplica. This is to ensure that all the possible
(collection,shard) pair combinations are added as hints so that policy engine
can select the right one.
# New tests added in ComputePlanActionTest to test auto-adding replicas for
multiple collections having single as well as multiple shards on new nodes.
I'll commit after running precommit and tests.
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
