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 <email address hidden>
Partial-Bug: #1853000
(cherry picked from commit 15e21010a8a8594678afe385821ee804ec9e16c7)
(cherry picked from commit 223e786c5716015c7ac1bdda94feabcd9c79716a)
Reviewed: https:/ /review. opendev. org/692119 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=2631cb8c544 430927336379333 82af341fff42bb
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 2631cb8c5444309 2733637933382af 341fff42bb
Author: Kamil Sambor <email address hidden>
Date: Thu Oct 17 15:30:58 2019 +0200
Add configurable monitor timeouts for ovn dbs
Under pressure, the default monitor timeout value of 20 seconds is not :profile: :pacemaker: :ovn_dbs_ bundle and by default is set to 60s.
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:
Change-Id: Ib95c6b7614631e ed264d42e6cf616 72b705e7893 678afe385821ee8 04ec9e16c7) c7ac1bdda94feab cd9c79716a)
Signed-off-by: Kamil Sambor <email address hidden>
Partial-Bug: #1853000
(cherry picked from commit 15e21010a8a8594
(cherry picked from commit 223e786c5716015