cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10847) Log a message when refusing a major compaction due to incremental repairedAt status
Date Thu, 14 Jan 2016 14:44:39 GMT

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

Marcus Eriksson commented on CASSANDRA-10847:
---------------------------------------------

Yeah, it might be, I wanted to have the same message in 3.2+ where we major compact to 2 files
per data directory. I will update the message

> Log a message when refusing a major compaction due to incremental repairedAt status
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10847
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10847
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Compaction
>            Reporter: Brandon Williams
>            Assignee: Marcus Eriksson
>            Priority: Trivial
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> When you do a major compaction, but have some repaired sstables and some that are not,
it will correctly not compact them together.  However, it can be somewhat confusing the operator
as to *why* they aren't compacting together.  It would be beneficial, specifically when doing
a major, to log that we aren't going to do a full major because of this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message