geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masaki Yamakawa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3845) local-destroy setting of eviction breaks the consistency of the partition region
Date Mon, 30 Oct 2017 22:57:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225905#comment-16225905
] 

Masaki Yamakawa commented on GEODE-3845:
----------------------------------------

I agree with that action item.
However, once confirmed again, the data is inconsistent even when eviction does not occur.
For example, change the maximumEntries of EvictionAttributes of BugExpireAndEvictionDUnitTest
to 10 -> 1000. In that case eviction does not occur, but the data is inconsistent.

https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java

> local-destroy setting of eviction breaks the consistency of the partition region
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-3845
>                 URL: https://issues.apache.org/jira/browse/GEODE-3845
>             Project: Geode
>          Issue Type: Bug
>          Components: eviction
>            Reporter: Masaki Yamakawa
>
> I use entry-idle-time and eviction together in a partition region that holds one redundant
copy.
> Details of setting are as follows:
> {code:xml}
> <region name="Data" refid="PARTITION">
>   <region-attributes>
>     <entry-idle-time>
>       <expiration-attributes timeout="60" action="destroy" />
>     </entry-idle-time>
>     <partition-attributes redundant-copies="1" />
>     <eviction-attributes>
>       <lru-entry-count maximum="10" action="local-destroy" />
>     </eviction-attributes>
>   </region-attributes>
> </region>
> {code}
> In this setting, the data held by the cache server is different. Then, inconsistent results
are returned depending on the server to be connected. Eviction of the partition region can
only select local-destroy or overflow-to-disk. On the other hand, it is written that the expire
chapter of the document can not use local-destroy, local-invalidate in the partition region.
Likewise, I think that data inconsistency will occur even with the settings like this time.
> Below is the test code:
> https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java
> I think that it is necessary to add a check at the time of region creation or write it
in the document.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message