Allocator Failures

Allocator failures result in alerts in the Cloud UI. You cannot repair an allocator in the Cloud UI, so you should first move all nodes to a new allocator. Vacate options for a selected allocator can help fine tune the removal of nodes. After the allocator is vacated, you should investigate the cause of the failure separately, which could be due to a host machine failure, and replace any lost capacity.

Note: There is currently no snapshot/restore support, so all vacate processes should check Gracefully move data and Skip snapshot, leaving Restore from latest snapshot unchecked. Also check Vacate target based on the value of RUNNER_NAME.