[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Smith updated GEODE-5541: ----------------------------- Fix Version/s: (was: 1.7.0) 1.8.0 > A create followed by a destroy of the same key in a transaction invokes cache > listener on remote node > ----------------------------------------------------------------------------------------------------- > > Key: GEODE-5541 > URL: https://issues.apache.org/jira/browse/GEODE-5541 > Project: Geode > Issue Type: Bug > Components: transactions > Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0 > Reporter: Eric Shu > Assignee: Eric Shu > Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > A create followed by a destroy of the same key in a transaction is treated as > a no op on the near side (transaction host), and no destroy event is invoked > on the transaction host. The destroy operation is distributed to remote nodes > (far side). The intend is to make sure a normal region can destroy the key if > it exists (far side). > Currently a destroy event is invoked for this no op on remote node even > though the node does not have the key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)