[
https://issues.apache.org/jira/browse/SOLR-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-9735:
-------------------------------
Description:
As SolrCloud is now used at fairly large scale, most users end up writing their
own cluster management tools. We should have a framework for cluster management
in Solr.
In a discussion with [~noble.paul], we outlined the following steps w.r.t. the
approach to having this implemented:
* *Basic API* calls for cluster management e.g. utilize added nodes, remove a
node etc. These calls would need explicit invocation by the users to begin with.
* *Metrics* and stats tracking e.g. qps, etc. These would be required for any
advanced cluster management tasks e.g. *maintain a qps of 'x'* by *auto-adding
a replica* (using a recipe) etc. We would need collection/shard/node level
views of metrics for this.
* *Recipes*: combination of multiple sequential/parallel API calls based on
rules. This would be complicated specially as most of these would be long
running series of tasks which would either have to be rolled back or resumed in
case of a failure.
* *Event based triggers* that would not require explicit cluster management
calls for end users.
was:
As SolrCloud is now used at fairly large scale, most users end up writing their
own cluster management tools. We should have a framework for cluster management
in Solr.
In a discussion with [~noble.paul], we outlined the following steps w.r.t. the
approach to having this implemented:
* *Basic API* calls for cluster management e.g. utilize added nodes, remove a
node etc. These calls would need explicit invocation by the users to begin with.
* *Metrics* and stats tracking e.g. qps, etc. These would be required for any
advanced cluster management tasks e.g. *maintain a qps of 'x'* by *auto-adding
a replica* (using a recipe) etc. We would need collection/shard/node level
views of metrics for this.
* *Recipes*: combination of multiple sequential/parallel API calls based on
rules.
* *Event based triggers* that would not require explicit cluster management
calls for end users.
> Umbrella JIRA for Cluster Management framework in SolrCloud
> -----------------------------------------------------------
>
> Key: SOLR-9735
> URL: https://issues.apache.org/jira/browse/SOLR-9735
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Anshum Gupta
>
> As SolrCloud is now used at fairly large scale, most users end up writing
> their own cluster management tools. We should have a framework for cluster
> management in Solr.
> In a discussion with [~noble.paul], we outlined the following steps w.r.t.
> the approach to having this implemented:
> * *Basic API* calls for cluster management e.g. utilize added nodes, remove a
> node etc. These calls would need explicit invocation by the users to begin
> with.
> * *Metrics* and stats tracking e.g. qps, etc. These would be required for any
> advanced cluster management tasks e.g. *maintain a qps of 'x'* by
> *auto-adding a replica* (using a recipe) etc. We would need
> collection/shard/node level views of metrics for this.
> * *Recipes*: combination of multiple sequential/parallel API calls based on
> rules. This would be complicated specially as most of these would be long
> running series of tasks which would either have to be rolled back or resumed
> in case of a failure.
> * *Event based triggers* that would not require explicit cluster management
> calls for end users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
