[
https://issues.apache.org/jira/browse/GEODE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321073#comment-17321073
]
ASF GitHub Bot commented on GEODE-8231:
---------------------------------------
albertogpz commented on pull request #783:
URL: https://github.com/apache/geode-native/pull/783#issuecomment-819593811
I wonder if it would make more sense to write a JIRA to fix the problem
caused by the GEODE-8231 PR instead of reverting 3 PRs that have been for
months in the develop branch.
I do not know if I understood correctly the issue but wouldn't a possible
solution be to change the eventId of the "leftover" keys (the keys for those
puts that were not sent because the server went down) before sending them in
the new thread to another server?
If we did so, we could keep the code in the "PRs to be reverted", fix the
issue and have a test case to verify that everything works as expected.
--
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)
