[
https://issues.apache.org/jira/browse/GEODE-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582990#comment-16582990
]
Darrel Schneider commented on GEODE-5224:
-----------------------------------------
It is unclear what you mean by "recovery". It looks like your region are not
persistent so I don't think you mean recovering at startup from a disk store.
Is this correct?
Do you mean by "eviction recovery" faulting in a value that was overflowed to
disk?
We do not yet understand how you tested this. If you could attach some code
that demonstrates what you do that would be great.
It sounds like you did this:
# start two servers with a redundant partitioned region that is not persistent
but has overflow with an entry lru count of 2.
# do 3 puts on the region
# look at the stats
Is that it? At this point will the stats be wrong? Or do you also do some gets?
> statistics of Type DiskRegionStatistics is not correct after recovery from
> eviction
> -----------------------------------------------------------------------------------
>
> Key: GEODE-5224
> URL: https://issues.apache.org/jira/browse/GEODE-5224
> Project: Geode
> Issue Type: Bug
> Components: eviction
> Reporter: yossi reginiano
> Priority: Major
> Labels: pull-request-available
> Attachments: EntriesInVM.png, EntriesOnlyOnDisk.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> we are using geode 1.4 and facing the following issue
> after getting into eviction we can see that entriesOnlyOnDisk is shown
> correctly, the problem is when getting out of eviction - we can see that the
> summarize is getting messed up and that entriesOnlyOnDisk is not reduced to 0
> but rather stay high and on the other end - entriesInVM is reduced under 0.
> the numbers sum up ok - the issue is only that we reduce too much from
> entriesInVM while part of it should have been removed from entriesOnlyOnDisk.
> the issue can be reproduced very simply by getting into and out of eviction
> and monitoring the statistics.
> please see following screen shots that describes the issue-
> !image-2018-05-16-15-02-35-522.png!
>
>
> !image-2018-05-16-15-03-18-815.png!
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
