default token value of 3000 is not a supported config

[shaunrampersad]

The default token value of 3000ms is not a supported config by redhat. This could result in clusters being installed that would not be supported.

As per article https://access.redhat.com/solutions/300953

Red Hat Enterprise Linux 5 and 6 using cman:

The default timeout is 10 seconds (10000 ms).

The following are the limits of the range tested by Red Hat Cluster Engineering:

Minimum: 5 seconds (5000 ms)
Maximum: 300 seconds (300000 ms)

There are known issues with values outside the tested range. If an issue is determined to be associated with values outside the tested range, Red Hat Support may require you reproduce the issue with a token timeout within the tested range.

My cluster is running on rhel6

[roidelapluie]

Hi,

Which version of this module are you using? We have troubles with CentOS 6 and this module.

[shaunrampersad]

Hi

I'm using 0.7.0. Its an old version, but I did check that the token is still at 3000 in master

[roidelapluie]

"
Red Hat Enterprise Linux 7 using Pacemaker:

The default token timeout for Pacemaker clusters is 1000ms, increasing by 650ms for each additional member of the cluster, unless specified otherwise in the corosync.conf
"

[roidelapluie]

This module is not working anymore with CentOS 6. Are you using CMAN? With which puppet module?

[shaunrampersad]

yes, using cman.
" With which puppet module?" I'm not sure what you mean by this?

[roidelapluie]

Which cman puppet module are you using?

[shaunrampersad]

Hi
Sorry for the delay. We arent using a cman puppet module. upon further investigation, I see that any value placed into corosync.conf will be ignored by cman, since cman uses cluster.conf.

I will close this issue as it is not related if using cman.

Thanks
Shaun