cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9625) GraphiteReporter not reporting
Date Mon, 02 Jan 2017 09:49:58 GMT


Stefan Podkowinski commented on CASSANDRA-9625:

[~llambiel], I can't see anything that would indicate any deadlocks in your provided thread
dump. In fact {{metrics-graphite-reporter-thread-1}} is just waiting for the next tick to
execute and pull the latest metrics from Cassandra. Are you sure this isn't a problem with
your Graphite installation? Are there any error messages in Cassandra related to Graphite?
Are there any connections from Cassandra to Graphite (as can be checked using netstat)?

> GraphiteReporter not reporting
> ------------------------------
>                 Key: CASSANDRA-9625
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Debian Jessie, 7u79-2.5.5-1~deb8u1, Cassandra 2.1.3
>            Reporter: Eric Evans
>            Assignee: Stefan Podkowinski
>         Attachments: Screen Shot 2016-04-13 at 10.40.58 AM.png, 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

View raw message