[
https://issues.apache.org/jira/browse/GEODE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962398#comment-16962398
]
ASF subversion and git services commented on GEODE-7357:
--------------------------------------------------------
Commit 4a413d9568a5556406a004d91cd9937fc8a9ca35 in geode's branch
refs/heads/feature/GEODE-7341 from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a413d9 ]
GEODE-7357: Updating the documentation for member-timeout (#4224)
GEODE-7357: Updating the documentation for member-timeout
Rewriting the documentation for the member-timeout property. The old
documentation did to accurately describe the health check process or the
amount of time it would take to remove an unresponsive member.
> membership-timeout documentation is incorrect
> ---------------------------------------------
>
> Key: GEODE-7357
> URL: https://issues.apache.org/jira/browse/GEODE-7357
> Project: Geode
> Issue Type: Bug
> Components: docs, membership
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The description for membership-timeout on
> https://geode.apache.org/docs/guide/110/reference/topics/gemfire_properties.html
> is incorrect.
> It describes the member-timeout behavior of an old version of the product,
> before geode 1.0.
> Based on this description, a user might assume that an unresponsive member
> will be kicked out of the system only after 3*member-timeout milliseconds
> have elapsed. That may have been true before geode 1.0, but the geode has a
> different failure detection algorithm which will remove members after a
> minimum of 2*member-timeout milliseconds
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
