Changes for page Cluster properties

From version 1.1
edited by gru
on 20.01.2021, 16:20
Change comment: Imported from XAR
To version 2.1
edited by jdr
on 13.07.2021, 16:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gru
1 +XWiki.jdr
Content
... ... @@ -25,16 +25,16 @@
25 25  |cluster.tcp.external.port|(same as cluster.tcp.bind.port)|no|External port when using TCP.
26 26  |cluster.tcp.initial.hosts|(empty list)|no|For discovering other cluster servers in the network. Required only when the protocol is set to TCP. A list of all expected cluster servers that are to be a part of the network. Multiple values are specified by using the same key on several lines.
27 27  |cluster.discovery.timeout|0|no|The number of milliseconds to wait for the connection to another server of the cluster to be established successfully. When set to {{code language="none"}}0{{/code}}, there is no timeout limit.
28 -|cluster.tcp.merge3.minInterval|1000|no|{{version major="6" minor="2"/}} For TCP connections: minimum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must not be a negative number.
29 -|cluster.tcp.merge3.maxInterval|30000|no|{{version major="6" minor="2"/}} For TCP connections: maximum time in milliseconds before sending an info message to other member in the cluster. AA cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must be a number greater than //0//.
30 -|cluster.tcp.fdall.interval|3000|no|{{version major="6" minor="2"/}} For TCP connections: Interval in milliseconds at which a HEARTBEAT is sent to other servers in the cluster. The cluster uses failure detection based on simple heartbeat protocol. Must be a number greater than //0//.
31 -|cluster.tcp.fdall.timeout|5000|no|{{version major="6" minor="2"/}} For TCP connections: Timeout in milliseconds after which a cluster server is suspected to be dead or not working anymore. Must not be a negative number.
32 -|cluster.tcp.gms.attempts|6|no|{{version major="6" minor="2"/}} For TCP connections: When a server wishes to join a cluster, the number of join attempts before we give up and become a singleton. //0// means //never give up//.
33 -|cluster.tcp.gms.timeout|10000|no|{{version major="6" minor="2"/}} For TCP connections: When a server wishes to join a cluster, the join timeout in milliseconds for a single join attempt. Must not be a negative number.
34 -|cluster.udp.merge3.minInterval|1000|no|{{version major="6" minor="2"/}} For UDP connections: minimum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must not be a negative number.
35 -|cluster.udp.merge3.maxInterval|30000|no|{{version major="6" minor="2"/}} For UDP connections: maximum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must be a number greater than //0//.
36 -|cluster.udp.fdall.interval|3000|no|{{version major="6" minor="2"/}} For UDP connections: Interval in milliseconds at which a HEARTBEAT is sent to other servers in the cluster. The cluster uses failure detection based on simple heartbeat protocol. Must be a number greater than //0//.
37 -|cluster.udp.fdall.timeout|5000|no|{{version major="6" minor="2"/}} For UDP connections: Timeout in milliseconds after which a cluster server is suspected to be dead or not working anymore. Must not be a negative number.
38 -|cluster.udp.gms.attempts|6|no|{{version major="6" minor="2"/}} For UDP connections: When a server wishes to join a cluster, the number of join attempts before we give up and become a singleton. //0// means //never give up//.
39 -|cluster.udp.gms.timeout|10000|no|{{version major="6" minor="2"/}} For TCP connections: When a server wishes to join a cluster, the join timeout in milliseconds for a single join attempt. Must not be a negative number.
28 +|cluster.tcp.merge3.minInterval|1000|no|For TCP connections: minimum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must not be a negative number.
29 +|cluster.tcp.merge3.maxInterval|30000|no|For TCP connections: maximum time in milliseconds before sending an info message to other member in the cluster. AA cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must be a number greater than //0//.
30 +|cluster.tcp.fdall.interval|3000|no|For TCP connections: Interval in milliseconds at which a HEARTBEAT is sent to other servers in the cluster. The cluster uses failure detection based on simple heartbeat protocol. Must be a number greater than //0//.
31 +|cluster.tcp.fdall.timeout|5000|no|For TCP connections: Timeout in milliseconds after which a cluster server is suspected to be dead or not working anymore. Must not be a negative number.
32 +|cluster.tcp.gms.attempts|6|no|For TCP connections: When a server wishes to join a cluster, the number of join attempts before we give up and become a singleton. //0// means //never give up//.
33 +|cluster.tcp.gms.timeout|10000|no|For TCP connections: When a server wishes to join a cluster, the join timeout in milliseconds for a single join attempt. Must not be a negative number.
34 +|cluster.udp.merge3.minInterval|1000|no|For UDP connections: minimum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must not be a negative number.
35 +|cluster.udp.merge3.maxInterval|30000|no|For UDP connections: maximum time in milliseconds before sending an info message to other member in the cluster. A cluster server periodically broadcasts its address and name to so that each server can discover the other servers in the cluster group. Must be a number greater than //0//.
36 +|cluster.udp.fdall.interval|3000|no|For UDP connections: Interval in milliseconds at which a HEARTBEAT is sent to other servers in the cluster. The cluster uses failure detection based on simple heartbeat protocol. Must be a number greater than //0//.
37 +|cluster.udp.fdall.timeout|5000|no|For UDP connections: Timeout in milliseconds after which a cluster server is suspected to be dead or not working anymore. Must not be a negative number.
38 +|cluster.udp.gms.attempts|6|no|For UDP connections: When a server wishes to join a cluster, the number of join attempts before we give up and become a singleton. //0// means //never give up//.
39 +|cluster.udp.gms.timeout|10000|no|For TCP connections: When a server wishes to join a cluster, the join timeout in milliseconds for a single join attempt. Must not be a negative number.
40 40  {{/table}}