[
https://issues.apache.org/jira/browse/GEODE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639075#comment-14639075
]
ASF subversion and git services commented on GEODE-92:
------------------------------------------------------
Commit b8686b52b97f8cbe1b46df8cda81a5e2bbd4cfaf in incubator-geode's branch
refs/heads/feature/GEODE-9 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b8686b5 ]
GEODE-56 Decrementing bytesOverflowedOnDisk when an update happens to an
evicted entry.
For persistent regions, we were correctly updating this stat. But for
non persistent regions we did not read the old size on disk, so we were
not updating the stat.
If the entry was in the async queue, we only increment the stat once
when the final value is actually written to disk. So we will only
decrement the stat if the oldValue is not pending asynchronous write to
disk.
I'm still seeing issues with the entryCount. I've tracked this down to
what I think is a problem with tombstones. It appears when we modify an
entry that is a tombstone, we increment the entry count once for the new
value, and once for removing the tombstone. I've filed GEODE-92 and
GEODE-93 for the issues I've found with this new test.
> PR with entry eviction 1 leaves 3 entries in memory with async overflow
> -----------------------------------------------------------------------
>
> Key: GEODE-92
> URL: https://issues.apache.org/jira/browse/GEODE-92
> Project: Geode
> Issue Type: Bug
> Reporter: Dan Smith
> Attachments:
> 0001-Test-that-demonstrates-two-many-entries-in-memory-wi.patch
>
>
> I discovered this while working on a unit test for another issue. It appears
> that when configuring a PR with entry eviction 1, in some cases there ends up
> being more than 1 entry left in memory when using overflow to disk with
> disk-synchronous=false.
> With synchronous disk, this issue does not occur.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
