lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Commented] (SOLR-11189) Provisioning actions for autoscaling
Date Fri, 04 Aug 2017 02:23:00 GMT


Shalin Shekhar Mangar commented on SOLR-11189:

Sounds cool!

We also need to ensure that the nodes provisioned or decommissioned by this action are not
discovered again by other nodeLost or nodeAdded triggers.

> Provisioning actions for autoscaling
> ------------------------------------
>                 Key: SOLR-11189
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Andrzej Bialecki 
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message