cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11127) index_summary_upgrade_test.py is failing
Date Fri, 27 May 2016 17:45:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs updated CASSANDRA-11127:
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.0.x)
                   3.0.7
                   3.7
           Status: Resolved  (was: Ready to Commit)

bq. Do you think it's worth to add this at this stage for 2.1 and 2.2 Tyler Hobbs? It's such
an esoteric edge case now I'm not sure sure it's worth the investment, probably not.

I think there would be a little value in that, but I also agree that it's probably not the
best investment of our time right now.  So, unless somebody else feels strongly about this,
I'm going to leave that out for now.

Anyway, thanks for the review.  I've committed this to 3.0 as {{6f236c801be5b80fe18afc3ecebd4032c19b434d}}
and merged up to 3.7 and trunk.

> index_summary_upgrade_test.py is failing
> ----------------------------------------
>
>                 Key: CASSANDRA-11127
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11127
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Philip Thompson
>            Assignee: Tyler Hobbs
>              Labels: dtest, windows
>             Fix For: 3.7, 3.0.7
>
>         Attachments: node1_debug.log
>
>
> index_summary_upgrade_test.py 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
[here|http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/157/testReport/index_summary_upgrade_test/TestUpgradeIndexSummary/test_upgrade_index_summary/].
> Locally I see the following:
> {code}
> 'ERROR [SSTableBatchOpen:2] 2016-02-05 15:29:04,304 CassandraDaemon.java:195 - Exception
in thread Thread[SSTableBatchOpen:2,5,main]\njava.lang.AssertionError: Illegal bounds [4..8);
size: 4\n\tat org.apache.cassandra.io.util.Memory.checkBounds(Memory.java:339) ~[main/:na]\n\tat
org.apache.cassandra.io.util.Memory.getInt(Memory.java:292) ~[main/:na]\n\tat org.apache.cassandra.io.sstable.IndexSummary.getPositionInSummary(IndexSummary.java:146)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.IndexSummary.getKey(IndexSummary.java:151)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader.validateSummarySamplingLevel(SSTableReader.java:928)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader.load(SSTableReader.java:748)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader.load(SSTableReader.java:705)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:491)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:374)
~[main/:na]\n\tat org.apache.cassandra.io.sstable.format.SSTableReader$4.run(SSTableReader.java:533)
~[main/:na]\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_66]\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_66]\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_66]\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]\n\tat
java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]']
> {code}
> Node log is attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message