[
https://issues.apache.org/jira/browse/CASSANDRA-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647675#comment-17647675
]
Thomas Steinmaurer commented on CASSANDRA-9881:
-----------------------------------------------
Interesting, I'm also getting this with 3.11.14 while trying to scrub a single
Cassandra table, where it seems that a single physical SSTable on disk is
broken. Seems to be in an infinite loop with the same log line as shown above.
No progress according to "nodetool compactionstats" etc ...
> 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: Low
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
