cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3758) parallel compaction hang (on large rows?)
Date Fri, 30 Mar 2012 14:10:36 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242362#comment-13242362
] 

Jonathan Ellis commented on CASSANDRA-3758:
-------------------------------------------

bq. there seems to be tons of CompactionReducer threads, coming for lots of different ParallelCompactionIterable,
which would suggest we don't shutdown the executor of CompactionReducer correctly. But I don't
see why that would happen

I assume they are using a version from before CASSANDRA-3711.

bq. attaching a patch to fix that problem

+1
                
> parallel compaction hang (on large rows?)
> -----------------------------------------
>
>                 Key: CASSANDRA-3758
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3758
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jackson Chung
>            Assignee: Sylvain Lebresne
>              Labels: compaction, datastax_qa
>             Fix For: 1.0.9
>
>         Attachments: 0001-Fix-totalBytes-count-for-ParallelCompactionIterable.txt, cassandra.log.zip
>
>
> it is observed that:
> nodetool -h 127.0.0.1 -p 8080 compactionstats
> pending tasks: 1
> compaction type keyspace column family bytes compacted bytes total progress
> Compaction SyncCoreComputedContactNetworks 119739938 0 n/a
> and that is not moving (ie the bytes compacted never increase, the bytes total stay 0).
> this is probably going to be difficult to reproduce, as the problem is observed when
compacting 15 large sstables (total ~300G).
> attaching the thread dumps (along with logs), when such happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message