cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Stepura (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-5493) Confusing output of CommandDroppedTasks
Date Wed, 27 Nov 2013 06:05:36 GMT

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

Mikhail Stepura edited comment on CASSANDRA-5493 at 11/27/13 6:04 AM:
----------------------------------------------------------------------

[~ondrej.cernos] what is your "seeds" configuration? Which IP addresses do you use (for seeds)
in _cassandra.yaml_?

I'm asking because trying to figure out what's your setup. 
There are quite a lot options for IP addresses and for places in YAML where to put them as
well

* Addresses
** Amazon private
** Amazon public
** Amazon elastic?
** Other?

* Settings
** Broadcast address
** Listen address
** IPs for seeds (Snitch settings)
** RPC address
 



was (Author: mishail):
[~ondrej.cernos] what is your "seeds" configuration? Which IP addresses do you use (for seeds)
in _cassandra.yaml_?

I'm asking because trying to figure out what's your setup. There quite a lot options for IP
addresses and for places in YAML where to put them

* Addresses
** Amazon private
** Amazon public
** Amazon elastic?
** Other?

* Settings
** Broadcast address
** Listen address
** IPs for seeds (Snitch settings)
** RPC address
 


> 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