ACK
On 09/10/14 15:28, Jan Friesse wrote:
With introduction of token_coefficient, token timeout defined in
configuration file may be no longer reflect real token timeout, what may
be confusing.
Enhanced description hopefully fix that.
Signed-off-by: Jan Friesse <[email protected]>
---
man/corosync.conf.5 | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/man/corosync.conf.5 b/man/corosync.conf.5
index 8fb7a0b..95eca2d 100644
--- a/man/corosync.conf.5
+++ b/man/corosync.conf.5
@@ -280,11 +280,17 @@ by reducing the token timeout.
.TP
token
-This timeout specifies in milliseconds until a token loss is declared after not
+This timeout is used directly or as a base for real token timeout calculation
(explained in
+.B token_coefficient
+section). Token timeout specifies in milliseconds until a token loss is
declared after not
receiving a token. This is the time spent detecting a failure of a processor
in the current configuration. Reforming a new configuration takes about 50
milliseconds in addition to this timeout.
+For real token timeout used by totem it's possible to read cmap value of
+.B runtime.config.token
+key.
+
The default is 1000 milliseconds.
.TP
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss
