[
https://issues.apache.org/jira/browse/CASSANDRA-11430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216715#comment-15216715
]
Nick Bailey edited comment on CASSANDRA-11430 at 3/29/16 7:38 PM:
------------------------------------------------------------------
This is happening because the progress notification mechanism has completely
changed. The old method signatures were left in place but this is fairly
pointless since old clients won't be able to understand the new progress/status
reporting mechanism.
Anyone have any idea on how much work it would be to pull back in the old
progress reporting mechanism for the old method signatures? I'm guessing quite
a bit.
was (Author: nickmbailey):
This is happening because the progress notification mechanism has completely
changed. The old method signatures were left in place but this is fairly
pointless since old clients won't be able to understand the new progress/status
reporting mechanism.
> forceRepairRangeAsync hangs sometimes
> -------------------------------------
>
> Key: CASSANDRA-11430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11430
> Project: Cassandra
> Issue Type: Bug
> Reporter: Nick Bailey
> 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)
