[
https://issues.apache.org/jira/browse/SOLR-10496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-10496:
-----------------------------------------
Attachment: SOLR-10496.patch
First cut of compute plan action. There are some impedance mismatches between
the node added event and the policy framework that need to be fixed before we
proceed further, such as:
# It should be possible to create a Suggester without knowing the collection
and shard names) -- when a node is added, all we know is that the default
implicit action is MOVEREPLICA but we don't know which collection/shard should
be moved to the new node
# An easier, perhaps iterator like API for generating multiple operations in a
row -- when a node is added, multiple movereplica operations might be performed
to balance the cluster.
# The policy API should consume a hint from the trigger e.g. the node name
which was added instead of trying to figure such things by itself looking at
the cluster state or metrics.
The TriggerAction API also needs refactoring as it is needlessly complex to
implement an action and we need a way to consume information from preceding
steps as well as pass along information to the next actions in the chain.
> Implement ComputePlanAction for autoscaling
> -------------------------------------------
>
> Key: SOLR-10496
> URL: https://issues.apache.org/jira/browse/SOLR-10496
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Labels: autoscaling
> Fix For: master (7.0)
>
> Attachments: SOLR-10496.patch
>
>
> The ComputePlanAction will use the cluster/collection policy to calculate the
> cluster operations to be performed. This issue is about integrating the work
> done in SOLR-10278 with the trigger framework.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
