From 0a53ba43cc8a93f47868ffbbeb7faea325529c81 Mon Sep 17 00:00:00 2001 From: Jiri Stransky Date: Tue, 5 Apr 2016 19:15:39 +0200 Subject: 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 --- puppet/hieradata/controller.yaml | 1 + 1 file changed, 1 insertion(+) (limited to 'puppet/hieradata/controller.yaml') 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 -- cgit 1.2.3-korg