geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-5505) Cache listener not invoked on a retried destroy() operation
Date Wed, 01 Aug 2018 20:32:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565937#comment-16565937
] 

ASF subversion and git services commented on GEODE-5505:
--------------------------------------------------------

Commit 08f110650834c6d03accef8e98c0cf4cc47bc3fb in geode's branch refs/heads/develop from
[~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=08f1106 ]

GEODE-5505 Cache listener not invoked on a retried destroy() operation

This started happening when we moved listener/client notification to
LocalRegion.basicDestroyPart2.  The code to handle duplicate destroys
from a client was only invoking basicDestroyPart3.

This closes #2233


> Cache listener not invoked on a retried destroy() operation
> -----------------------------------------------------------
>
>                 Key: GEODE-5505
>                 URL: https://issues.apache.org/jira/browse/GEODE-5505
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> If a server fails while a client is performing a destroy() operation it's possible for
other servers to  have recovered consistency using a distributed synchronization operation
before the client is able to retry the operation.  If this happens we accept the destroy()
operation in the other servers but we're not invoking cache listeners.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message