This is an automated email from the ASF dual-hosted git repository.
onichols pushed a commit to branch support/1.14
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.14 by this push:
new fbef055 GEODE-8374 - User Guide: ViewAckTimeout Configuration (#6099)
fbef055 is described below
commit fbef0554e024e50103804bed52734692f074edcb
Author: Dave Barnes <[email protected]>
AuthorDate: Sat Mar 6 08:32:28 2021 -0800
GEODE-8374 - User Guide: ViewAckTimeout Configuration (#6099)
(cherry picked from commit df0d3c0271c822ed7614951f36f8d59f35ab0637)
---
.../how_network_partitioning_management_works.html.md.erb | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
a/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb
b/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb
index e42b413..590bee1 100644
---
a/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb
+++
b/geode-docs/managing/network_partitioning/how_network_partitioning_management_works.html.md.erb
@@ -43,7 +43,16 @@ The overall process for detecting a network partition is as
follows:
where {0} is the number of processes that failed and {1} lists the
processes.
4. Whenever the coordinator is alerted of a membership change (a member
either joins or leaves the cluster), the coordinator generates a new membership
view. The membership view is generated by a two-phase protocol:
- 1. In the first phase, the membership coordinator sends out a view
preparation message to all members and waits 12 seconds for a view preparation
ack return message from each member. If the coordinator does not receive an ack
message from a member within 12 seconds, the coordinator attempts to connect to
the member's failure-detection socket. If the coordinator cannot connect to the
member's failure-detection socket, the coordinator declares the member dead and
starts the membership [...]
+ 1. In the first phase, the membership coordinator sends out a view
preparation message to all
+ members and waits for a view preparation acknowledgement from each member.
If the coordinator
+ does not receive an ack message from a member (within a specified timeout
period -- see below),
+ the coordinator attempts to connect to the member's failure-detection
socket. If the coordinator
+ cannot connect to the member's failure-detection socket, the coordinator
declares the member
+ dead and starts the membership view protocol again from the beginning.<br
/><br />
+ The timeout period for acknowledgement of a view change, the ack view
timeout period, is based
+ on the value of the `member-timeout` system property, and defaults to
about 12 seconds (12437ms).
+ The allowable range for the view ack timeout setting is 1500ms to
12437ms.<br /><br />
+
2. In the second phase, the coordinator sends out the new membership view
to all members that acknowledged the view preparation message or passed the
connection test.
5. Each time the membership coordinator sends a view, each member calculates
the total weight of members in the current membership view and compares it to
the total weight of the previous membership view. Some conditions to note:
