cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11430) Add legacy notifications backward-support on deprecated repair methods
Date Tue, 05 Apr 2016 20:33:25 GMT

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

Paulo Motta updated CASSANDRA-11430:
------------------------------------
    Summary: Add legacy notifications backward-support on deprecated repair methods  (was:
forceRepairRangeAsync hangs sometimes)

> Add legacy notifications backward-support on deprecated repair methods
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-11430
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11430
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Nick Bailey
>            Assignee: Paulo Motta
>             Fix For: 3.x
>
>
> forceRepairRangeAsync is deprecated in 2.2/3.x series. It's still available for older
clients though. Unfortunately it sometimes hangs when you call it. It looks like it completes
fine but the notification to the client that the operation is done is never sent. This is
easiest to see by using nodetool from 2.1 against a 3.x cluster.
> {noformat}
> [Nicks-MacBook-Pro:16:06:21 cassandra-2.1] cassandra$ ./bin/nodetool repair -st 0 -et
1 OpsCenter
> [2016-03-24 16:06:50,165] Nothing to repair for keyspace 'OpsCenter'
> [Nicks-MacBook-Pro:16:06:50 cassandra-2.1] cassandra$
> [Nicks-MacBook-Pro:16:06:55 cassandra-2.1] cassandra$
> [Nicks-MacBook-Pro:16:06:55 cassandra-2.1] cassandra$ ./bin/nodetool repair -st 0 -et
1 system_distributed
> ...
> ...
> {noformat}
> (I added the ellipses)



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

Mime
View raw message