diff options
| author |   John Eckersberg <jeckersb@redhat.com> | 2017-07-19 11:28:39 -0400 |
|---|---|---|
| committer | John Eckersberg <jeckersb@redhat.com> | 2017-07-19 11:28:39 -0400 |
| commit | ef582bfc6a25958fbb3d701b6b95328ef72c1fc8 (patch) | |
| tree | b5f2ad618824cc5fd819a7c591b7946e76744d5a /releasenotes/notes/composable-veritas-hyperscale-driver-e7f0a35d7d9a8df1.yaml | |
| parent | 7e4f7dd2b0324247bba8fd8da5f3becd20e8299f (diff) | |
Increase default RabbitMQ/Erlang TCP timeout from 5 to 15 seconds
This should be greater than the default value of
corosync_token_timeout, which is 10 seconds. That way, if an entire
cluster node is unavailable, appropriate fencing measures can occur.
With the current settings, it is possible for brief network
interruptions, greater than 5 seconds, but less than 10 seconds, to
occur. This can cause the RabbitMQ cluster to fail in subtle ways,
but no corrective action taken by pacemaker.
Change-Id: I735d43616c5c623c4398d924713012f595b2e5f9
Diffstat (limited to 'releasenotes/notes/composable-veritas-hyperscale-driver-e7f0a35d7d9a8df1.yaml')
0 files changed, 0 insertions, 0 deletions