[SOLR-11189] Provisioning actions for autoscaling

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 8.1, 9.0
• Component/s: AutoScaling
• Assignee: Unassigned
• Reporter: Andrzej Bialecki
• Created: 03/Aug/17 16:36
• Updated: 12/May/22 00:26
• Resolved: 14/Aug/21 01:33

Description

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.

Issue Links

• is related to: SOLR-9735 Umbrella JIRA for Auto Scaling and Cluster Management in SolrCloud