[jira] [Commented] (CASSANDRA-9405) AssertionError: Data component is missing

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547752#comment-14547752 ] 

Sam Tunnicliffe commented on CASSANDRA-9405:
--------------------------------------------

+1 opening the keyspace before scrubbing is unnecessary & looks like a leftover from some refactoring during CASSANDRA-8049 dev  (and as such it won't affect earlier versions). 

> AssertionError: Data component is missing
> -----------------------------------------
>
>                 Key: CASSANDRA-9405
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9405
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Marcus Eriksson
>             Fix For: 2.2.x
>
>         Attachments: 0001-don-t-open-system-ks-before-scrubbing-the-data-direc.patch, node2.log
>
>
> In a [counter dtest|http://cassci.datastax.com/job/trunk_dtest/135/testReport/counter_tests/TestCounters/upgrade_test/] that drains and restarts nodes several times, we're occasionally seeing errors in the logs after restarting like the following:
> {noformat}
> ERROR [SSTableBatchOpen:2] 2015-05-15 16:54:41,087 DebuggableThreadPoolExecutor.java:242 - Error in ThreadPoolExecutor
> java.lang.AssertionError: Data component is missing for sstable/tmp/dtest-r8mRyB/test/node2/data/system/sstable_activity-5a1ff267ace03f128563cfae6103c65e/la-5-big
>     at org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:414) ~[main/:na]
>     at org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:346) ~[main/:na]
>     at org.apache.cassandra.io.sstable.format.SSTableReader$4.run(SSTableReader.java:476) ~[main/:na]
>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ~[na:1.7.0_76]
>     at java.util.concurrent.FutureTask.run(FutureTask.java:262) ~[na:1.7.0_76]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) ~[na:1.7.0_76]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_76]
>     at java.lang.Thread.run(Thread.java:745) [na:1.7.0_76]
> {noformat}
> Looking at the node's logs (attached), the {{sstable_activity}} table started a compaction just prior to the node being drained, and {{la-5-big}} is probably the partial compaction result.
> I set the fix version as 2.2, but the problem may exist in earlier C* versions.



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