cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Wulf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9625) GraphiteReporter not reporting
Date Fri, 08 Apr 2016 18:23:25 GMT

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

Brandon Wulf commented on CASSANDRA-9625:
-----------------------------------------

I too upgraded to 2.1.13 hoping to fix this issue. 

I upgraded from 2.1.8 primarily because the graphite metrics reporter kept dropping and for
a few weeks I saw no more issues. Then, after we added some new nodes with SSDs, this seems
to be effecting the fast nodes. Maybe the old nodes were having enough io wait time injected
to negate a race condition causing this issue?

> GraphiteReporter not reporting
> ------------------------------
>
>                 Key: CASSANDRA-9625
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9625
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Debian Jessie, 7u79-2.5.5-1~deb8u1, Cassandra 2.1.3
>            Reporter: Eric Evans
>            Assignee: T Jake Luciani
>         Attachments: metrics.yaml, thread-dump.log
>
>
> When upgrading from 2.1.3 to 2.1.6, the Graphite metrics reporter stops working.  The
usual startup is logged, and one batch of samples is sent, but the reporting interval comes
and goes, and no other samples are ever sent.  The logs are free from errors.
> Frustratingly, metrics reporting works in our smaller (staging) environment on 2.1.6;
We are able to reproduce this on all 6 of production nodes, but not on a 3 node (otherwise
identical) staging cluster (maybe it takes a certain level of concurrency?).
> Attached is a thread dump, and our metrics.yaml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message