[
https://issues.apache.org/jira/browse/CASSANDRA-14597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563594#comment-16563594
]
Stefan Podkowinski commented on CASSANDRA-14597:
------------------------------------------------
2.2 seems to consume space in segments much faster compared to 3.x, so it's
allocating a new segment within shorter time and the test passes.
3.x allocates a new segment early, while still writing into an existing one.
Maybe this behaviour has been changed in CASSANDRA-10202?
3.0 will slowly continue to write to the segment and eventually will allocate a
new segment if the timeout is sufficiently long. I'd therefor propose to change
the timeout to 120 seconds to make the test pass.
> [dtest] snapshot_test.TestArchiveCommitlog
> ------------------------------------------
>
> Key: CASSANDRA-14597
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14597
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jason Brown
> Priority: Minor
> Labels: dtest
> Attachments: 2_2.txt, 3_0.txt, 3_11_3.txt
>
>
> All TestArchiveCommitLog dtests fail on 3.0, but no other branches. Output
> from pytest error:
> {noformat}
> assert (
> time.time() <= stop_time), "It's been over a {s}s and we
> haven't written a new " + \
> > "commitlog segment. Something is wrong.".format(s=timeout)
> E AssertionError: It's been over a {s}s and we haven't written a
> new commitlog segment. Something is wrong.
> tools/hacks.py:61: AssertionError
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
