cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg DeAngelis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4952) Add blocking force compaction (and anything else) calls to NodeProbe
Date Wed, 21 Aug 2013 02:42:51 GMT

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

Greg DeAngelis commented on CASSANDRA-4952:
-------------------------------------------

I think I misinterpreted what was being asked for. After digging further I realized that the
compaction command exposed via nodetool already does a blocking compaction. Given that, is
this ticket still valid?
                
> Add blocking force compaction (and anything else) calls to NodeProbe
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-4952
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4952
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.6
>            Reporter: Michael Harris
>            Priority: Minor
>              Labels: lhf
>
> There are times when I'd like to get feedback about when compactions complete.  For example,
if I'm deleting data from cassandra and want to know when it is 100% removed from cassandra
(tombstones collected and all).  This is completely trivial to implement based on the existing
code (the method called by the non-blocking version returns a future, so you could just wait
on that, potentially with a timeout).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message