AWS: Temporary connectivity issues cause spurious restarts

Details

Detail name Value
Changelog Number 18917
Type Bug
Status Resolved
Affected Versions
Fix Versions Exasol 8.25.0
Resolution Date 2024-02-15

Description

Directly after one of the nodes is unreachable for a very short time (which could e.g. be caused by abnormally high load on a node), the database may occasionally stop the node that is actually running correctly and fail to start them again.

Workaround

Restart the nodes manually in the AWS console.

Fix

The failover functionality has been fixed to not restart any nodes in these situations until the cluster as a whole is in a defined state again.