cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10005) Streaming not enough bytes error
Date Thu, 06 Aug 2015 19:34:05 GMT


Yuki Morishita commented on CASSANDRA-10005:

I think so, yes.
There is no clean up for CompressedInputStream when something goes wrong.

> Streaming not enough bytes error
> --------------------------------
>                 Key: CASSANDRA-10005
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chris Moos
>            Priority: Minor
>             Fix For: 2.2.x
>         Attachments: deadlock.txt, errors.txt
> I'm adding a new node to the cluster and I'm seeing a bunch of the errors below and the
node never joins. It looks like a deadlock.
> After looking through the code it looks like IncomingFileMessage will tell the session
to retry on Exceptions (except IOException) but the CompressedInputStream thread is still
running and then the retry happens and the deadlock ensues. It might be best to close the
StreamReader (and stop the thread) if an Exception happens before retrying.
> I'm not sure why I am getting this error to begin with though, might it have something
to do with not being able to upgrade my SSTables after going from 2.1.2 -> 2.2.0?
> {code}
> error: null
> -- StackTrace --
> java.lang.AssertionError
>         at org.apache.cassandra.db.lifecycle.LifecycleTransaction.checkUnused(
>         at org.apache.cassandra.db.lifecycle.LifecycleTransaction.split(
>         at org.apache.cassandra.db.compaction.CompactionManager.parallelAllSSTableOperation(
>         at org.apache.cassandra.db.compaction.CompactionManager.performSSTableRewrite(
>         at org.apache.cassandra.db.ColumnFamilyStore.sstablesRewrite(
>         at org.apache.cassandra.service.StorageService.upgradeSSTables(
> {code}

This message was sent by Atlassian JIRA

View raw message