[
https://issues.apache.org/jira/browse/CASSANDRA-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748614#comment-16748614
]
Laxmikant Upadhyay commented on CASSANDRA-9881:
-----------------------------------------------
I am also observing this issue on 3.11.2 . Sstables were corrupted as disk got
full due to snapshots, and when i run nodetool scrub after deleting snapshots i
get below WARN in infinite loop.
{code:java}
WARN [CompactionExecutor:2677] 2019-01-22 10:08:16,907 OutputHandler.java:52 -
Row starting at position 24772608 is unreadable; skipping to next
WARN [CompactionExecutor:2677] 2019-01-22 10:08:16,908 OutputHandler.java:57 -
Error reading row (stacktrace follows):
java.io.IOError: java.io.IOException: Unable to read row key from data file
at org.apache.cassandra.db.compaction.Scrubber.scrub(Scrubber.java:216)
~
{code}
> Rows with negative-sized keys can't be skipped by sstablescrub
> --------------------------------------------------------------
>
> Key: CASSANDRA-9881
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9881
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
