Add posibilities to set ovndbs monitor interval
Add posibilities to configure ovn dbs monitor interval
in tht by OVNDBSPacemakerMonitorInterval (default 30s).
Under load, this can create extra stress and since the
timeout has already been bumped, it makes sense to bump
this interval to a higher value as a trade off
between detecting a failure and stressing the service.
Depends-On: https://review.opendev.org/#/c/779918/
Change-Id: Id836676826f6e7c97ef8e3d665ab3e467ad055ba
(cherry picked from commit 9ece6f97af
)
This commit is contained in:
parent
5651573e2d
commit
780b057461
|
@ -106,6 +106,14 @@ parameters:
|
|||
default: ''
|
||||
description: Override the private key size used when creating the
|
||||
certificate for this service
|
||||
OVNDBSPacemakerMonitorIntervalSlave:
|
||||
description: monitor interval for ovn dbs resource in seconds
|
||||
type: number
|
||||
default: 30
|
||||
OVNDBSPacemakerMonitorIntervalMaster:
|
||||
description: monitor interval for ovn dbs resource in seconds
|
||||
type: number
|
||||
default: 10
|
||||
|
||||
conditions:
|
||||
puppet_debug_enabled: {get_param: ConfigDebug}
|
||||
|
@ -168,6 +176,8 @@ outputs:
|
|||
- tripleo::profile::pacemaker::ovn_dbs_bundle::dbs_timeout: {get_param: OVNDBSPacemakerTimeout}
|
||||
- tripleo::profile::pacemaker::ovn_dbs_bundle::replication_probe_interval: {get_param: OVNDBSReplicationInterval}
|
||||
- tripleo::profile::pacemaker::ovn_dbs_bundle::force_ocf: true
|
||||
- tripleo::profile::pacemaker::ovn_dbs_bundle::monitor_interval_slave: {get_param: OVNDBSPacemakerMonitorIntervalSlave}
|
||||
- tripleo::profile::pacemaker::ovn_dbs_bundle::monitor_interval_master: {get_param: OVNDBSPacemakerMonitorIntervalMaster}
|
||||
- tripleo::haproxy::ovn_dbs_manage_lb:
|
||||
if:
|
||||
- use_external_load_balancer
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Add posibilities to configure ovn dbs monitor interval
|
||||
in tht by OVNDBSPacemakerMonitorInterval (default 30s).
|
||||
Under load, this can create extra stress and since the
|
||||
timeout has already been bumped, it makes sense to bump
|
||||
this interval to a higher value as a trade off
|
||||
between detecting a failure and stressing the service.
|
Loading…
Reference in New Issue