cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-1740) Nodetool commands to query and stop compaction, repair, cleanup and scrub
Date Wed, 23 Nov 2011 09:17:41 GMT


Sylvain Lebresne updated CASSANDRA-1740:

    Attachment: 0001-Patch-to-Stop-compactions-v4.patch

Looks good except that I believe logExceptionAfterExecute uses one too many getCause() so
that the UserInterruptedException is not actually catched. Attaching v4 that solves this as
well as the following minor changes:
* make UserInteruptedException takes a CompactionInfo directly and generate the message internally
(instead of duplicating the same message at each call site).
* remove an added and non used logger in CompactionInfo
* update the nodetool help message to respect the convention for mandatory arguments. 
> Nodetool commands to query and stop compaction, repair, cleanup and scrub
> -------------------------------------------------------------------------
>                 Key: CASSANDRA-1740
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Chip Salzenberg
>            Assignee: Vijay
>            Priority: Minor
>              Labels: compaction
>             Fix For: 1.0.4
>         Attachments: 0001-Patch-to-Stop-compactions-v2.patch, 0001-Patch-to-Stop-compactions-v3.patch,
0001-Patch-to-Stop-compactions-v4.patch, 0001-Patch-to-Stop-compactions.patch, CASSANDRA-1740.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> The only way to stop compaction, repair, cleanup, or scrub in progress is to stop and
restart the entire Cassandra server.  Please provide nodetool commands to query whether such
things are running, and stop them if they are.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message