[CASSANDRA-11430] Add legacy notifications backward-support on deprecated repair methods

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.6, 3.0.6, 3.6
• Component/s: Legacy/Observability, Legacy/Streaming and Messaging
• Severity: Normal
• Assignee: Paulo Motta
• Reporter: Nick Bailey

Authors

Paulo Motta

Reviewers

Yuki Morishita

• Created: 24/Mar/16 21:19
• Updated: 16/Apr/19 09:30
• Resolved: 11/Apr/16 16:43

Description

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.

[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
...
...

(I added the ellipses)

Issue Links

• is related to: CASSANDRA-13121 repair progress message breaks legacy JMX support
• is related to: CASSANDRA-11530 Remove deprecated repair method in 4.0