[
https://issues.apache.org/jira/browse/CASSANDRA-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881012#comment-13881012
]
Ondřej Černoš commented on CASSANDRA-5493:
------------------------------------------
[~mishail]: Finally I have my testing environment up and running again. I
switched to elastic IPs for seeds as you recommend above (and also due to
CASSANDRA-5768 which rendered the private-IP setup useless in multiple DC
cluster setup).
The output of the bean now contains 7 records: all public IPs of all 6 nodes in
both datacenters and the private IP of the node the bean is investigated on.
Tested on 1.2.11.
> 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.5#6160)
