[
https://issues.apache.org/jira/browse/GEODE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-92:
-----------------------------------
Description:
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.
A deadlock was also found when doing a put on a region with custom expiry
callback doing getValue().
was:
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.
> 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
> Components: eviction
> Reporter: Dan Smith
> Assignee: Sai Boorlagadda
> Priority: Major
> Fix For: 1.0.0-incubating.M3
>
> 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.
> A deadlock was also found when doing a put on a region with custom expiry
> callback doing getValue().
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
