95a7f217e2
Under pressure, the default monitor timeout value of 20 seconds is not
enough to prevent unnecessary failovers of the ovn-dbs pacemaker resource.
While spawning a few VMs in the same time this could lead to unnecessary
movements of master DB, then re-connections of ovn-controllers (slaves are
read-only), further peaks of load on DBs, and at the end it could lead to
snowball effect. Now this value can be configurable by dbs_timeout in
tripleo::profile::pacemaker::ovn_dbs_bundle and by default is set to 60s.
Change-Id: Ib95c6b7614631eed264d42e6cf61672b705e7893
Signed-off-by: Kamil Sambor <ksambor@redhat.com>
Partial-Bug: #1853000
(cherry picked from commit 15e21010a8
)
10 lines
559 B
YAML
10 lines
559 B
YAML
---
|
|
features:
|
|
- |
|
|
Under pressure, the default monitor timeout value of 20 seconds is not
|
|
enough to prevent unnecessary failovers of the ovn-dbs pacemaker resource.
|
|
While spawning a few VMs in the same time this could lead to unnecessary
|
|
movements of master DB, then re-connections of ovn-controllers (slaves are
|
|
read-only), further peaks of load on DBs, and at the end it could lead to
|
|
snowball effect. Now this value can be configurable by dbs_timeout in
|
|
tripleo::profile::pacemaker::ovn_dbs_bundle and by default is set to 60s. |