Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 6 Nov 2014 16:50:34 +0000 (UTC)
From: "Michael Shuler (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12643191.1366287892000.435112.1415292634912@Atlassian.JIRA>
In-Reply-To: <JIRA.12643191.1366287892000@Atlassian.JIRA>
References: <JIRA.12643191.1366287892000@Atlassian.JIRA>
 <JIRA.12643191.1366287892991@arcas>
Subject: [jira] [Resolved] (CASSANDRA-5493) Confusing output of
 CommandDroppedTasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-5493?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Shuler resolved CASSANDRA-5493.
---------------------------------------
       Resolution: Incomplete
    Reproduced In: 1.2.11, 1.2.9  (was: 1.2.9, 1.2.11)

[~ondrej.cernos] please, reopen this ticket if further help is needed.

> 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=C5=99ej =C4=8Cerno=C5=A1
>            Priority: Minor
>
> We have 2 DCs, 3 nodes in each, using EC2 support. We are debugging nodet=
ool repair problems (roughly 1 out of 2 attempts just freezes). We looked i=
nto the MessagingServiceBean to see what is going on using jmxterm. See the=
 following:
> {noformat}
> #mbean =3D org.apache.cassandra.net:type=3DMessagingService:
> CommandDroppedTasks =3D {=20
>  107.aaa.bbb.ccc =3D 0;
>  166.ddd.eee.fff =3D 124320;
>  10.ggg.hhh.iii =3D 0;
>  107.jjj.kkk.lll =3D 0;
>  166.mmm.nnn.ooo =3D 1336699;
>  166.ppp.qqq.rrr =3D 1329171;
>  10.sss.ttt.uuu =3D 0;
>  107.vvv.www.xxx =3D 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 pu=
blic IPs and once with their private IPs. The nodes in remote DC (the 166 o=
nes) are reported only once. I am pretty sure this is a bug - the node shou=
ld 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.3.4#6332)