You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kenneth Failbus (JIRA)" <ji...@apache.org> on 2015/07/21 21:09:05 UTC
[jira] [Commented] (CASSANDRA-7909) Do not exit nodetool repair
when receiving JMX NOTIF_LOST
[ https://issues.apache.org/jira/browse/CASSANDRA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635625#comment-14635625 ]
Kenneth Failbus commented on CASSANDRA-7909:
--------------------------------------------
This issue is still not fixed in 2.0.14. we have a 48 node cluster. When nodetool repair is run, notification is lost.
2015-07-21 18:25:19,627] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:37:19,636] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:41:19,647] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:43:19,649] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:45:19,651] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:49:19,655] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:52:19,657] Lost notification. You should check server log for repair status of keyspace xxxxx
[2015-07-21 18:53:19,659] Lost notification. You should check server log for repair status of keyspace xxxxx
> 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: 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)