1d19b702b1
Stop failovers if the count of simultaneously failed amphora reaches the number configured in the new failover_threshold option. This may prevent large scale accidental failover events, like in the case of network failures or read-only database issues. Story: 2005604 Task: 30837 Co-Authored-By: Tatsuma Matsuki <matsuki.tatsuma@jp.fujitsu.com> Co-Authored-By: Tom Weininger <tweining@redhat.com> Change-Id: I0d2c332fa72e47e70d594579ab819a6ece094cdd
13 lines
658 B
YAML
13 lines
658 B
YAML
---
|
|
features:
|
|
- |
|
|
A new configuration option ``failover_threshold`` can be set to limit the
|
|
number of amphorae simultaneously pending failover before halting the
|
|
automatic failover process. This should help prevent unwanted mass failover
|
|
events that can happen in cases like network interruption to an AZ or the
|
|
database becoming read-only. This feature is not enabled by default, and it
|
|
should be configured carefully based on the size of the environment.
|
|
For example, with 100 amphorae a good threshold might be 20 or 30, or
|
|
a value greater than the typical number of amphorae that would be expected
|
|
on a single host.
|