[
https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721443#comment-16721443
]
Benedict commented on CASSANDRA-14931:
--------------------------------------
FYI, I have added a 2.2 backport into the mix. This was actually very smooth,
but to keep the code as simple as possible I have modified the 2.2 unit tests
to require JDK8. I think this is pretty reasonable, since we typically build
with JDK8 and a 1.7 target for the jar.
There's definitely a problem with 3.0, however. 2.2 succeeds with an infinite
loop (at least until resource exhaustion, until we get 14922), but
{{coordinatorWrite}} kills 3.0 rapidly with the read failing to return the
recently written values. Presumably this is an issue with the way we execute
the queries.
> Backport In-JVM dtests to 2.2, 3.0 and 3.11
> -------------------------------------------
>
> Key: CASSANDRA-14931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14931
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> Fix For: 2.2.14, 3.0.18, 3.11.4
>
>
> The In-JVM dtests are of significant value, and much of the testing we are
> exploring with it can easily be utilised on all presently maintained
> versions. We should backport the functionality to at least 3.0.x and 3.11.x
> - and perhaps even consider 2.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
