[
https://issues.apache.org/jira/browse/GEODE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616681#comment-15616681
]
ASF subversion and git services commented on GEODE-2043:
--------------------------------------------------------
Commit 2ef50b24de1457ab91729f22a3c2ff4a8a07557b in incubator-geode's branch
refs/heads/feature/GEM-983 from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=2ef50b2 ]
GEODE-2043: change makeTombstone to handle exception
Now if makeTombstone has an exception but had already changed
the region entry value to a TOMBSTONE, it will now change
the value to REMOVE_PHASE2 instead of leaving it as a TOMBSTONE.
> severe Internal product error log message possible when async disk configured
> on persistent region
> --------------------------------------------------------------------------------------------------
>
> Key: GEODE-2043
> URL: https://issues.apache.org/jira/browse/GEODE-2043
> Project: Geode
> Issue Type: Bug
> Components: persistence
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Fix For: 1.1.0-incubating
>
>
> It is possible to see a log message like this:
> [severe 2016/10/22 07:18:14.665 UTC gemfire3_client-10_8522 <P2P message
> reader for client-10(gemfire1_client-10_8469:8469)<ec><v2>:1028 shared
> ordered uid=10 port=50942> tid=0x66] Internal product error: attempt to
> directly remove a versioned tombstone from region entry map
> java.lang.Exception: stack trace
> at
> org.apache.geode.internal.cache.AbstractRegionMap.removeEntry(AbstractRegionMap.java:261)
> This log message can be safely ignored. It happens if async disk is
> configured on a persistent geode region. If an entry on that region is being
> destroyed and the region is being closed or destroyed at the same time, then
> this message may be logged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
