cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ondřej Černoš (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5493) Confusing output of CommandDroppedTasks
Date Tue, 26 Nov 2013 09:40:36 GMT

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

Ondřej Černoš commented on CASSANDRA-5493:
------------------------------------------

_listen_address_ is set to the address configured on eth0, _broadcast_address_ is set to the
elastic IP assigned to the instance. I use the Ec2MultiRegionSnitch. Everything works well.


> 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š
>            Assignee: Mikhail Stepura
>            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.1#6144)

Mime
View raw message