diff options
| author |   Emilien Macchi <emilien@redhat.com> | 2016-10-12 12:32:18 -0400 |
|---|---|---|
| committer | Emilien Macchi <emilien@redhat.com> | 2016-10-12 12:32:18 -0400 |
| commit | 12910de9230ab5e04b0f8a78cc6245186f4cea34 (patch) | |
| tree | 0f72f57689a7f76dcf085da45aaf6c2379d6154c /manifests/profile/pacemaker/database | |
| parent | 8a4d7ae04f773385d1a6677ad635859d753337ab (diff) | |
pacemaker: increase timeouts for rabbitmq and redis
When we observe the 'stop timeout' values of pacemaker resources:
rabbitmq and redis, they are set to 90s. But for all other services, it
is set to 200s.
The overcloud deployment sometimes fails due to this with the error:
Error: Could not complete shutdown of rabbitmq-clone, 1 resources
remaining
Error performing operation: Timer expired
This patch updates the timeout for Redis and RabbitMQ to avoid this
error.
Change-Id: I8a3b3951a896ee3e8e5e09778e8ea4717e76a1b4
Diffstat (limited to 'manifests/profile/pacemaker/database')
| -rw-r--r-- | manifests/profile/pacemaker/database/redis.pp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/manifests/profile/pacemaker/database/redis.pp b/manifests/profile/pacemaker/database/redis.pp index e081516..261df30 100644 --- a/manifests/profile/pacemaker/database/redis.pp +++ b/manifests/profile/pacemaker/database/redis.pp @@ -60,6 +60,7 @@ class tripleo::profile::pacemaker::database::redis ( master_params => '', meta_params => 'notify=true ordered=true interleave=true', resource_params => 'wait_last_known_master=true', + op_params => 'start timeout=200s stop timeout=200s', require => Class['::redis'], } } |