You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2014/09/10 23:20:34 UTC

[jira] [Created] (CASSANDRA-7909) Do not exit nodetool repair when receiving JMX NOTIF_LOST

Yuki Morishita created CASSANDRA-7909:
-----------------------------------------

             Summary: Do not exit nodetool repair when receiving JMX NOTIF_LOST
                 Key: CASSANDRA-7909
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7909
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Yuki Morishita
            Assignee: Yuki Morishita
            Priority: Trivial
             Fix For: 1.2.19, 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 https://weblogs.java.net/blog/emcmanus/archive/2007/08/when_can_jmx_no.html. So we should just continue to listen to events until repair finishes or connection is really closed.



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