You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2014/07/30 01:38:39 UTC

[jira] [Commented] (CASSANDRA-5493) Confusing output of CommandDroppedTasks

    [ https://issues.apache.org/jira/browse/CASSANDRA-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078615#comment-14078615 ] 

Michael Shuler commented on CASSANDRA-5493:
-------------------------------------------

Ping [~ondrej.cernos] :)  If you can reproduce this in the latest 1.2.x release (currently 1.2.18) and provide the info requested by Mikhail, that would be great!  Thanks!

> Confusing output of CommandDroppedTasks
> ---------------------------------------
>
>                 Key: CASSANDRA-5493
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5493
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.3
>            Reporter: Ondřej Černoš
>            Priority: Minor
>
> We have 2 DCs, 3 nodes in each, using EC2 support. We are debugging nodetool repair problems (roughly 1 out of 2 attempts just freezes). We looked into the MessagingServiceBean to see what is going on using jmxterm. See the following:
> {noformat}
> #mbean = org.apache.cassandra.net:type=MessagingService:
> CommandDroppedTasks = { 
>  107.aaa.bbb.ccc = 0;
>  166.ddd.eee.fff = 124320;
>  10.ggg.hhh.iii = 0;
>  107.jjj.kkk.lll = 0;
>  166.mmm.nnn.ooo = 1336699;
>  166.ppp.qqq.rrr = 1329171;
>  10.sss.ttt.uuu = 0;
>  107.vvv.www.xxx = 0;
> };
> {noformat}
> The problem with this output is it has 8 records. The node's neighbours (the 107 and 10 nodes) are mentioned twice in the output, once with their public IPs and once with their private IPs. The nodes in remote DC (the 166 ones) are reported only once. I am pretty sure this is a bug - the node should be reported only with one of its addresses in all outputs from Cassandra and it should be consistent.



--
This message was sent by Atlassian JIRA
(v6.2#6252)