-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default token value of 3000 is not a supported config #300
Comments
Hi, Which version of this module are you using? We have troubles with CentOS 6 and this module. |
Hi I'm using 0.7.0. Its an old version, but I did check that the token is still at 3000 in master |
" 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 |
This module is not working anymore with CentOS 6. Are you using CMAN? With which puppet module? |
yes, using cman. |
Which cman puppet module are you using? |
Hi I will close this issue as it is not related if using cman. Thanks |
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:
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
The text was updated successfully, but these errors were encountered: