[jira] [Created] (HADOOP-11400) GraphiteSink does not reconnect to Graphite after 'broken pipe'

2014-12-12 Thread Kamil Gorlo (JIRA) 
Kamil Gorlo created HADOOP-11400:


 Summary: GraphiteSink does not reconnect to Graphite after 'broken 
pipe'
 Key: HADOOP-11400
 URL: https://issues.apache.org/jira/browse/HADOOP-11400
 Project: Hadoop Common
  Issue Type: Bug
  Components: metrics
Affects Versions: 2.5.1
Reporter: Kamil Gorlo


I see that after network error GraphiteSink does not reconnects to Graphite 
server and in effect metrics are not sent. 

Here is stacktrace I see (this is from nodemanager):

2014-12-11 16:39:21,655 ERROR 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter: Got sink exception, retry 
in 4806ms
org.apache.hadoop.metrics2.MetricsException: Error flushing metrics
at 
org.apache.hadoop.metrics2.sink.GraphiteSinkFixed.flush(GraphiteSinkFixed.java:120)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:184)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
at 
org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:129)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at 
org.apache.hadoop.metrics2.sink.GraphiteSinkFixed.flush(GraphiteSinkFixed.java:118)
... 5 more
2014-12-11 16:39:26,463 ERROR 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter: Got sink exception and over 
retry limit, suppressing further error messages
org.apache.hadoop.metrics2.MetricsException: Error flushing metrics
at 
org.apache.hadoop.metrics2.sink.GraphiteSinkFixed.flush(GraphiteSinkFixed.java:120)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:184)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
at 
org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:129)
at 
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at 
org.apache.hadoop.metrics2.sink.GraphiteSinkFixed.flush(GraphiteSinkFixed.java:118)
... 5 more

GraphiteSinkFixed.java is simply GraphiteSink.java from Hadoop 2.6.0 (with 
fixed https://issues.apache.org/jira/browse/HADOOP-11182) because I cannot 
simply upgrade Hadoop (I am using CDH5).



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

[jira] [Created] (HADOOP-11360) GraphiteSink reports data with wrong timestamp

2014-12-08 Thread Kamil Gorlo (JIRA) 
Kamil Gorlo created HADOOP-11360:


 Summary: GraphiteSink reports data with wrong timestamp
 Key: HADOOP-11360
 URL: https://issues.apache.org/jira/browse/HADOOP-11360
 Project: Hadoop Common
  Issue Type: Bug
  Components: metrics
Reporter: Kamil Gorlo


I've tried to use GraphiteSink with metrics2 system, but it looks that 
timestamp sent to Graphite is refreshed rarely (about every 2 minutes approx.) 
no mather how small period is set.

Here is my configuration:

*.sink.graphite.server_host=graphite-relay.host
*.sink.graphite.server_port=2013
*.sink.graphite.metrics_prefix=graphite.warehouse-data-1
*.period=10
nodemanager.sink.graphite.class=org.apache.hadoop.metrics2.sink.GraphiteSink

And here is dumpet network traffic to graphite-relay.host (only select lines, 
every line appears in 10 seconds as period suggests):

graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041472
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041472
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041472
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 3 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 4 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 2 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 3 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 2 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 2 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 1 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 1 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041600
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041728
graphite.warehouse-data-1.yarn.NodeManagerMetrics.Context=yarn.Hostname=warehouse-data-1.AllocatedContainers
 0 1418041728


As you can see, AllocatedContainers value is refreshed every 10 seconds, but 
timestamp is not.



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