This adds automated cluster member evacuation which migrates remote-backed instances if a cluster member is offline for a certain amount of time.
Currently, offline cluster members are not automatically evacuated. This however would be beneficial if the offline cluster member has remote-backed instances. These can be migrated even if the member is offline.
The following new configuration will be added:
The automated cluster member evacuation can be enabled by setting the configuration key to a positive integer. If this value is lower than
cluster.offline_threshold, that value will be used internally instead. This value represents the time is seconds after which an offline cluster member may be evacuated automatically.
If enabled, the cluster leader checks for offline members every minute, and evacuates those members if needed. Remote-backed instances are then migrated, and local instances are ignored as those cannot be migrated.
Once the offline member comes back online, it won’t be restored automatically. This needs to be done manually.
No API changes.
No CLI changes.
No database changes.
No upgrade handling.