You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Nick Reich (JIRA)" <ji...@apache.org> on 2018/02/07 20:11:02 UTC
[jira] [Commented] (GEODE-4621) CI Failure:
OplogJUnitTest.testEntryAlreadyWrittenIsCorrectlyUnmarkedForOverflowOnly
[ https://issues.apache.org/jira/browse/GEODE-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355996#comment-16355996 ]
Nick Reich commented on GEODE-4621:
-----------------------------------
This test (and maybe others that have not yet been identified) are failing due to asynchronous scans occuring on entry recently used flags being marked. If the scan occurs in between events in the test, this can cause the order of events to be evicted to not match what the test expects (and due to the approximate nature of our LRU algorithm both new and old, absolute order is not something we guarantee). This issue can be fixed by the following enhancement to LRUListWithAsyncSorting: prevent scans from being scheduled unless the size of the eviction list is greater than the number of entries we will scan when getting an evictable entry. This will also cut down on likely unneeded scan when the list is very small.
> CI Failure: OplogJUnitTest.testEntryAlreadyWrittenIsCorrectlyUnmarkedForOverflowOnly
> ------------------------------------------------------------------------------------
>
> Key: GEODE-4621
> URL: https://issues.apache.org/jira/browse/GEODE-4621
> Project: Geode
> Issue Type: Bug
> Components: eviction, persistence
> Affects Versions: 1.5.0
> Reporter: Nick Reich
> Priority: Major
>
> This test is intermittently failing due to an NPE. This test began to fail with commit 69443dadad91c1fba548c5562267938bfbe53f6a (GEODE-4598). GEODE-4598 turned on by default a new eviction algorithm which would now be used in all tests that utilize eviction but do not manually set the system property to choose an algorithm (such as this test). It needs to be determined why the new algorithm causes this failure and to fix the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)