diff options
| author |   Jiri Stransky <jistr@redhat.com> | 2016-04-05 19:15:39 +0200 |
|---|---|---|
| committer | Jiri Stransky <jistr@redhat.com> | 2016-04-06 10:46:32 +0200 |
| commit | 0a53ba43cc8a93f47868ffbbeb7faea325529c81 (patch) | |
| tree | f9eac00e406b3486921d86f37684fa8839124f4a /puppet/hieradata | |
| parent | 517f6b27a92fc7a12c0a561d90bde106ef35bf54 (diff) | |
Increase corosync token timeout
This might prevent dropping members from corosync cluster on high load
environments. Symptoms of this problem happening can sometimes be found
in corosync log:
dub 05 17:23:45 overcloud-controller-0 corosync[14152]: [MAIN ] Corosync
main process was not scheduled for 3691.8391 ms (threshold is 1320.0000
ms). Consider token timeout increase.
The default in the Puppet manifest is 1 second, which matches the
corosync default, and we override it with hiera to 10 seconds.
Change-Id: I5ea850ada657e5eecafa3e8b28613a0ac48e78f3
Diffstat (limited to 'puppet/hieradata')
| -rw-r--r-- | puppet/hieradata/controller.yaml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/puppet/hieradata/controller.yaml b/puppet/hieradata/controller.yaml index 5e87793a..8766263a 100644 --- a/puppet/hieradata/controller.yaml +++ b/puppet/hieradata/controller.yaml @@ -122,6 +122,7 @@ pacemaker::corosync::cluster_name: 'tripleo_cluster' pacemaker::corosync::manage_fw: false pacemaker::resource_defaults::defaults: resource-stickiness: { value: INFINITY } +corosync_token_timeout: 10000 # horizon horizon::cache_backend: django.core.cache.backends.memcached.MemcachedCache |