cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Stepura (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7336) RepairTask doesn't send a correct message in a JMX notifcation in case of IllegalArgumentException
Date Mon, 02 Jun 2014 04:55:01 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Stepura updated CASSANDRA-7336:
---------------------------------------

    Fix Version/s:     (was: 2.1.0)

> RepairTask doesn't send a correct message in a JMX notifcation in case of IllegalArgumentException
> --------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7336
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7336
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Mikhail Stepura
>            Priority: Minor
>             Fix For: 2.0.9
>
>
> From CASSANDRA-7317:
> The behavior when manually trying to repair the full range of 127.0.0.01 definitely needs
improvement though.
> Repair command:
> {noformat}
> [Nicks-MacBook-Pro:21:50:44 cassandra-2.0] cassandra$ bin/nodetool -p 7100 repair -st
-10 -et -9223372036854775808 system_traces
> [2014-05-28 21:50:55,803] Starting repair command #17, repairing 1 ranges for keyspace
system_traces
> [2014-05-28 21:50:55,804] Starting repair command #17, repairing 1 ranges for keyspace
system_traces
> [2014-05-28 21:50:55,804] Repair command #17 finished
> [Nicks-MacBook-Pro:21:50:56 cassandra-2.0] cassandra$ echo $?
> 1
> {noformat}
> system.log:
> {noformat}
> ERROR [Thread-96] 2014-05-28 21:40:05,921 StorageService.java (line 2621) Repair session
failed:
> java.lang.IllegalArgumentException: Requested range intersects a local range but is not
fully contained in one; this would lead to imprecise repair
> {noformat}
> * The actual output of the repair command doesn't really indicate that there was an issue.
Although the command does return with a non zero exit status.
> * The error here is invisible if you are using the synchronous jmx repair api. It will
appear as though the repair completed successfully.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message