You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/02/13 00:23:19 UTC

[jira] [Commented] (CASSANDRA-6698) Many too small SSTables when full repair

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

Jonathan Ellis commented on CASSANDRA-6698:
-------------------------------------------

Can you elaborate as to why CASSANDRA-4341 and CASSANDRA-5371 aren't helping?

> Many too small SSTables when full repair
> ----------------------------------------
>
>                 Key: CASSANDRA-6698
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6698
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Roman Skvazh
>            Priority: Minor
>         Attachments: cassa-many-small-sstables.txt
>
>
> We have troubles when cassandra drops messages because there is too many (over 10,000 on one column family) small (from 1Kb to 200Kb, and normal sizes too) and many pending compactions (over 700).
> We are using Leveled compaction with 160Mb sstable size.
> PS. Temp fix: stop repair, disable thrift,gossip and wait for compactions to be finished. Because this, we can not run full repair for about a month :(



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)