You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2018/06/22 05:21:00 UTC

[jira] [Updated] (SOLR-11189) Provisioning actions for autoscaling

     [ https://issues.apache.org/jira/browse/SOLR-11189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul updated SOLR-11189:
------------------------------
    Issue Type: New Feature  (was: Sub-task)
        Parent:     (was: SOLR-9735)

> Provisioning actions for autoscaling
> ------------------------------------
>
>                 Key: SOLR-11189
>                 URL: https://issues.apache.org/jira/browse/SOLR-11189
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Andrzej Bialecki 
>            Priority: Major
>             Fix For: master (8.0)
>
>
> Autoscaling should be able to provision new nodes when necessary, or decommission no longer needed nodes. Solr should support a few common platforms out of the box (eg. AWS and Azure) with an API for integration with other platforms.
> Auto-provisioning can already be implemented as a {{TriggerAction}}, however there are common non-trivial aspects that should be supported by the framework, such as:
> * authentication to cluster manager APIs
> * ability to consider cost vs. performance tradeoffs and constraints (avoiding over-provisioning and under-provisioning)
> * maintaining cluster stability (avoiding trashing) while reacting with small delay and lag. These aspects will likely require some form of feedback loop controller.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org