cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip S Doctor (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7909) Do not exit nodetool repair when receiving JMX NOTIF_LOST
Date Mon, 06 Oct 2014 18:25:34 GMT


Philip S Doctor commented on CASSANDRA-7909:

Hi, I have a question about this ticket.  

Apologies if this is a poor question, I don't usually touch c* code.

NodeProbe is listening to notifications from StorageProxyMBean and JMX connection notifications.

Let's say it loses notification that repair is complete.  In this case, when will the connection
close?  Does C* close the connection automatically when repair is complete?  If not it seems
like this could be a problem.

> Do not exit nodetool repair when receiving JMX NOTIF_LOST
> ---------------------------------------------------------
>                 Key: CASSANDRA-7909
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Trivial
>             Fix For: 2.0.11, 2.1.1
>         Attachments: 0001-Do-not-quit-nodetool-when-JMX-notif_lost-received.patch
> {{nodetool repair}} prints out 'Lost notification...' and exits when JMX NOTIF_LOST message
is received. But we should not exit right away since that message just indicates some messages
are lost because "they arrive so fast that they cannot be delivered to the remote client quickly
enough" according to
So we should just continue to listen to events until repair finishes or connection is really

This message was sent by Atlassian JIRA

View raw message