[
https://issues.apache.org/jira/browse/CASSANDRA-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897872#comment-17897872
]
Berenguer Blasi commented on CASSANDRA-20055:
---------------------------------------------
Given
[caffeine|https://www.javadoc.io/doc/com.github.ben-manes.caffeine/caffeine/latest/com.github.benmanes.caffeine/com/github/benmanes/caffeine/cache/Caffeine.html]
bq. Note that the cache may evict an entry before this limit is exceeded or
temporarily exceed the threshold while evicting. As the cache size grows close
to the maximum, the cache evicts entries that are less likely to be used again.
For example, the cache may evict an entry because it hasn't been used recently
or very often
And that eviction [can't be deterministically
triggered|https://github.com/ben-manes/caffeine/issues/64], unless the test
changing cache execution threads to which it has no access, the test is
inherently nondeterministic and that seems to show up in heavily loaded
environments which makes sense. I will push PRs to change the test to monitor
for evictions _to happen_ and not _how many_. That should suffice imo.
> Flaky PstmtPersistenceTest
> --------------------------
>
> Key: CASSANDRA-20055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20055
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0.15, 4.1.8, 5.0.3, 5.1
>
>
> PstmtPersistenceTest was found to be flaky in CASSANDRA-19986. It was
> multiplexed there 500 times * branches but it seems it can still fail
> https://app.circleci.com/pipelines/github/instaclustr/cassandra/4921/workflows/90e7e7c8-e897-45b1-991d-953340dd1d5c
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
