cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11127) is failing
Date Fri, 27 May 2016 00:44:12 GMT


Paulo Motta commented on CASSANDRA-11127:

This would probably be better served by a unit test with a manually generated broken ka sstable,
and then check if the index summary is being rebuilt correctly. Do you think it's worth to
add this at this stage for 2.1 and 2.2 [~thobbs]? It's such an esoteric edge case now I'm
not sure sure it's worth the investment, probably not.

In any case, getting rid of the dtest definitely makes sense given its flakey nature and 3.0+
removal code and tests look good, so I will mark this as ready to commit.

> is failing
> ----------------------------------------
>                 Key: CASSANDRA-11127
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Philip Thompson
>            Assignee: Tyler Hobbs
>              Labels: dtest, windows
>             Fix For: 3.0.x
>         Attachments: node1_debug.log
> is failing on the cassandra-3.0 branch, when run without
vnodes. The exception I'm seeing on cassci is different than locally. The cassci failure is
> Locally I see the following:
> {code}
> 'ERROR [SSTableBatchOpen:2] 2016-02-05 15:29:04,304 - Exception
in thread Thread[SSTableBatchOpen:2,5,main]\njava.lang.AssertionError: Illegal bounds [4..8);
size: 4\n\tat ~[main/:na]\n\tat ~[main/:na]\n\tat
~[main/:na]\n\tat java.util.concurrent.Executors$
~[na:1.8.0_66]\n\tat ~[na:1.8.0_66]\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker( ~[na:1.8.0_66]\n\tat
java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_66]\n\tat [na:1.8.0_66]']
> {code}
> Node log is attached.

This message was sent by Atlassian JIRA

View raw message