cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9881) Rows with negative-sized keys can't be skipped by sstablescrub
Date Thu, 05 May 2016 09:50:12 GMT


Brent Evans commented on CASSANDRA-9881:

I'm also experiencing the same issue when performing a Scrub, which results in the nodetool
scrub infinitely looping over the unreadable row.

Is there any plan to further investigate this, or is the only way to resolve this to find
and delete the affected SSTable?

Cassandra version: 2.1.11


WARN  [CompactionExecutor:3653] 2016-05-05 07:04:18,180 - Row starting
at position 809762816 is unreadable; skipping to next
WARN  [CompactionExecutor:3653] 2016-05-05 07:04:18,184 - Error reading
row (stacktrace follows): Unable to read row key from data file
	at org.apache.cassandra.db.compaction.Scrubber.scrub( ~[apache-cassandra-2.1.11.jar:2.1.11]
	at org.apache.cassandra.db.compaction.CompactionManager.scrubOne(
	at org.apache.cassandra.db.compaction.CompactionManager.access$300(
	at org.apache.cassandra.db.compaction.CompactionManager$3.execute(
	at org.apache.cassandra.db.compaction.CompactionManager$
	at [na:1.8.0_31]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( [na:1.8.0_31]
	at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_31]
	at [na:1.8.0_31]
Caused by: Unable to read row key from data file
	... 9 common frames omitted


> Rows with negative-sized keys can't be skipped by sstablescrub
> --------------------------------------------------------------
>                 Key: CASSANDRA-9881
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Brandon Williams
>            Priority: Minor
>             Fix For: 2.1.x
> It is possible to have corruption in such a way that scrub (on or offline) can't skip
the row, so you end up in a loop where this just keeps repeating:
> {noformat}
> WARNING: Row starting at position 2087453 is unreadable; skipping to next 
> Reading row at 2087453 
> row (unreadable key) is -1 bytes
> {noformat}
> The workaround is to just delete the problem sstable since you were going to have to
repair anyway, but it would still be nice to salvage the rest of the sstable.

This message was sent by Atlassian JIRA

View raw message