[
https://issues.apache.org/jira/browse/CASSANDRA-11430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218158#comment-15218158
]
Paulo Motta commented on CASSANDRA-11430:
-----------------------------------------
The {{StorageService}} registers a {{ProgressListener}} on {{RepairRunnable}}
which actually performs the actual triggering of JMX notifications in the new
format via {{JMXProgressSupport}}. We could add a {{LegacyJMXProgressSupport}}
that implements {{ProgressListener}} and translates {{ProgressEvent}} into
notifications in the old format with moderate-to-low effort.
We should have had removed these deprecated repair methods on 3.0, but now
they're probably going to stick all the way up to 4.0, so I'm not sure what's
the best thing to do here, since fixing these will just postpone adoption of
new methods until 4.0. :)
WDYT [~yukim]? Unsafe assassinate those on 3.X (since compatibility is broken
anyway), or add backward support?
> forceRepairRangeAsync hangs sometimes
> -------------------------------------
>
> 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)
