[ https://issues.apache.org/jira/browse/CASSANDRA-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321990#comment-16321990 ]
Tipwimon J. commented on CASSANDRA-9625: ---------------------------------------- I did some prove by sending metric from cassandra graphite-reporter (18 nodes) to both graphite server and logstash server. I found that the metrics which send to graphite server stopped reporting randomly on some node whereas the metrics which send to logstash is working fine on all 18 nodes. Then I checked in graphite log, it seems the connection was closed cleanly from cassandra and then no longer send metric from that node. > GraphiteReporter not reporting > ------------------------------ > > Key: CASSANDRA-9625 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9625 > Project: Cassandra > Issue Type: Bug > Components: Metrics > Environment: Debian Jessie, 7u79-2.5.5-1~deb8u1, Cassandra 2.1.3 > Reporter: Eric Evans > Fix For: 3.0.x, 3.11.x, 4.x > > Attachments: Screen Shot 2016-04-13 at 10.40.58 AM.png, metrics.yaml, > thread-dump.log, thread-dump2.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.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org