[
https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321056#comment-17321056
]
ASF GitHub Bot commented on GEODE-8231:
---------------------------------------
pdxcodemonkey commented on pull request #783:
URL: https://github.com/apache/geode-native/pull/783#issuecomment-819570757
> This PR also reverts code from GEODE-8565, which was an addition over
GEODE-8231 solution.
> So I think this PR should contain the revert of GEODE-8688, GEODE-8565 and
GEODE-8231.
Agree, this is the revert of all 3 of these. This is just a title change
for the PR, though, right? I have reviewed the 3 earlier PRs and see no
remaining code from them...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> C++ native client keeps trying to connect to down cache server hosting a
> partitioned region
> -------------------------------------------------------------------------------------------
>
> Key: GEODE-8231
> URL: https://issues.apache.org/jira/browse/GEODE-8231
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Alberto Gomez
> Assignee: Alberto Gomez
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> If a C++ client connected to a cluster is sending operations to a partitioned
> region and one of the server goes down, the client keeps trying to send
> operations to the down server. This can be observed in the logs by a
> continuous flow of lines containing: "IO error in handshake with endpoint..."
> The Java client, once it detects a server is down, it deletes it from the
> client metadata so there are no tries to connect to the server until the
> server is up again which is notified via a metadata refresh.
> The aim of this ticket is to align the behavior of the C++ native client to
> the Java client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
