[EXASOL-2423] Exasol on AWS 6.1.0-8: Enhanced Failover Capabilities Created: 27.01.2019 Updated: 24.01.2020 Resolved: 01.02.2019
|Fix Version/s:||Exasol 6.1.0|
|Reporter:||Captain EXASOL||Assignee:||Captain EXASOL|
Before a spare node had to be running all the time to provide automatic fail-safety capabilities in case of a node failure.
Starting with 6.1 on AWS failover capabilities are also available if:
In case an active node fails and a runnig spare node is available the spare node automatically replaces the failed node as usual (standard behaviour also before Exasol 6.1),
New behaviour with Exasol 6.1:
In case an active node fails and no running spare node can be detected the failed node will be restarted by the cloud failover plugin (that means the virtual machine will be stopped and started again). In most cases, the instance is migrated to a new underlying host computer when it's started.
If after this process step the node still fails the system checks whether a cold spare node is available. A cold spare node is a spare node that was configured and then suspended thus causing no costs for a running VM instance (storage costs still apply). In case a cold standby node can be found it is started and the standard fail-over mechanism is triggered.
Prerequisites for cold standby nodes and node reprovisioning:
Advantages/Disadvantages of a hot spare node
A running hot spare node provides the shortest service interruption in case of a node failure. On the other hand it causes the highest costs.