[
https://issues.apache.org/jira/browse/CASSANDRA-11641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256581#comment-15256581
]
Paulo Motta edited comment on CASSANDRA-11641 at 4/25/16 4:53 PM:
------------------------------------------------------------------
It seems you have a corrupted sstable on {{system.compactions_in_progress}}
table, most likely {{system-compactions_in_progress-ka-11383}} or
{{system-compactions_in_progress-ka-11384}}. Can you try scrubbing ({{nodetool
scrub}}) these sstables or the {{system.compactions_in_progress}} table and see
if it helps?
If online scrub does not work you may try stopping the node and running
[offline
scrub|https://engineering.gosquared.com/dealing-corrupt-sstable-cassandra].
was (Author: pauloricardomg):
It seems you have a corrupted sstable on {{system.compactions_in_progress}}
table, most likely {{system-compactions_in_progress-ka-11383}} or
{{system-compactions_in_progress-ka-11384}}. Can you try scrubbing ({{nodetool
scrub}}) these sstables or the {{system.compactions_in_progress}} table and see
if it helps?
If online scrub does not work you may try
> java.lang.IllegalArgumentException: Not enough bytes in system.log
> ------------------------------------------------------------------
>
> Key: CASSANDRA-11641
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11641
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: centos 6.5 cassandra2.1.13
> Reporter: peng xiao
> Attachments: system.log
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
