You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (Jira)" <ji...@apache.org> on 2020/08/13 22:32:00 UTC

[jira] [Resolved] (GEODE-8427) change redis to disconnect client instead of failing with memberDeparted

     [ https://issues.apache.org/jira/browse/GEODE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darrel Schneider resolved GEODE-8427.
-------------------------------------
    Fix Version/s: 1.14.0
       Resolution: Fixed

> change redis to disconnect client instead of failing with memberDeparted
> ------------------------------------------------------------------------
>
>                 Key: GEODE-8427
>                 URL: https://issues.apache.org/jira/browse/GEODE-8427
>             Project: Geode
>          Issue Type: Improvement
>          Components: redis
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.14.0
>
>
> Currently when a redis operation fails because one of the servers departed while it was in progress an exception is thrown that contains "memberDeparted". Clients are required to handle this non-standard error message and decide if the operation should be retried or not.
> A better approach is to have the server close the client connection that the operation came in on. Some clients already handle this and support things like auto reconnect. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)