[GitHub] [geode] mcmellawatt commented on pull request #3397: GEODE-6423 availability checks sometimes immediately initiate removal

["mcmellawatt (GitHub)" <gi...@apache.org>]

>From the PR title it sounds like the issue was that we aren't pinging the suspect member enough times before giving up (immediately initiating removal).  Why doesn't the giveupTime handle that problem?  We should continue to retry for up to the configured member timeout.  Since we are &&'ing all these conditions together, won't it still break if the timeout is exceeded even if retryIfConnectFails is true?  Forgive me if these are amateur questions, not super familiar with this code.

[ Full content available at: https://github.com/apache/geode/pull/3397 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org