Created attachment 732591 [details]
Description of problem:
When corosync is running in VM, it can happen, that VM (and thus corosync) is not scheduled for long time (longer then token timeout). Because in such environments, it's very hard to find out, if token was lost because of network overload or because of guest OS didn't scheduled corosync process or because host OS didn't scheduled VM, it would be nice improvement to implement pause detector in corosync. Corosync then displays warning message, when it was not scheduled for long enough time (0.8 * token_timeout). This will give us idea, if problem was network or scheduling and together with guest load monitoring should give as idea if problem was in guest or host.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Pause corosync
2. Unpause corosync
Token is lost, but it's not clear why.
Message "Corosync main process was not scheduled for X ms (threshold is Y ms). Consider token timeout increase." should be displayed.
Verified with scheduler-pause-detector.sh
FAIL on corosync-1.4.1-15.el6.x86_64 (RHEL6.4)
PASS on corosync-1.4.1-17.el6.x86_64 (RHEL6.5)
Sep 11 18:15:31 virt-014 corosync: [MAIN ] Corosync main process was not scheduled for 11066.0088 ms (threshold is 8000.0000 ms). Consider token timeout increase
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.