[
https://issues.apache.org/jira/browse/CASSANDRA-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622145#comment-14622145
]
Branimir Lambov commented on CASSANDRA-9717:
--------------------------------------------
I am sorry, the seed discussion only applies to compressed versions of the
test, which {{default_segment_size_test}} isn't.
I looked at the test and am wondering why it expects an overall size of 60mb
for two segments of 32mb each? It appears to error out as it sees 64, which is
correct and as expected.
60 (or maybe 62.5 as the test appears to allow for 12 or 13 segments) is
correct for {{small_segment_size_test}}.
The compressed version of this test, however, fails as the last segment of the
log is smaller. This is also expected-- compressed segments grow as data is
added; we probably need to special-case this.
> TestCommitLog segment size dtests fail on trunk
> -----------------------------------------------
>
> Key: CASSANDRA-9717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9717
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Branimir Lambov
> Priority: Blocker
> Fix For: 3.0 beta 1
>
>
> The test for the commit log segment size when the specified size is 32MB. It
> fails for me locally and on on cassci. ([cassci
> link|http://cassci.datastax.com/view/trunk/job/trunk_dtest/305/testReport/commitlog_test/TestCommitLog/default_segment_size_test/])
> The command to run the test by itself is {{CASSANDRA_VERSION=git:trunk
> nosetests commitlog_test.py:TestCommitLog.default_segment_size_test}}.
> EDIT: a similar test,
> {{commitlog_test.py:TestCommitLog.small_segment_size_test}}, also fails with
> a similar error.
> The solution here may just be to change the expected size or the acceptable
> error -- the result isn't far off. I'm happy to make the dtest change if
> that's the solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
