cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed Ferdous (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9625) GraphiteReporter not reporting
Date Thu, 13 Aug 2015 16:10:46 GMT

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

Ahmed Ferdous commented on CASSANDRA-9625:
------------------------------------------

I just wanted to add here that, in our case, as soon as we restarted the cassandra instances
on the "not sending metrics to graphite any more" nodes, they started working again. The only
difference is that, we started seeing the symptoms when we were putting some heavy write loads
(40k+ per second). We will run those load tests again today and I will keep you guys posted
if we can reproduce it.

> 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