[
https://issues.apache.org/jira/browse/CASSANDRA-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711887#comment-14711887
]
Jean-Francois Gosselin commented on CASSANDRA-9625:
---------------------------------------------------
[~tjake] I think that I've found the issue. When the Gauge metric for
CompressionMetadataOffHeapMemoryUsed is called, the following method is called
in org.apache.cassandra.io.util.Memory :
{code:title=org.apache.cassandra.io.util.Memory.java|borderStyle=solid}
public long size()
{
assert peer != 0;
return size;
}
{code}
and for some reason peer was 0. After the AssertionError the metrics graphite
reporter thread is no longer executed.
> 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)
