Neha Narkhede created KAFKA-655:
-----------------------------------
Summary: IOException due to yammer metrics on Kafka brokers
Key: KAFKA-655
URL: https://issues.apache.org/jira/browse/KAFKA-655
Project: Kafka
Issue Type: Bug
Affects Versions: 0.8
Environment: I set up a Kafka 0.8 cluster of 2 brokers and I see the
following error in the logs. Not sure how bad the impact is, but it will be
good to assess why this happens
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:883)
at
com.yammer.metrics.reporting.CsvReporter.createStreamForMetric(CsvReporter.java:142)
at
com.yammer.metrics.reporting.CsvReporter.getPrintStream(CsvReporter.java:271)
at
com.yammer.metrics.reporting.CsvReporter.access$000(CsvReporter.java:24)
at
com.yammer.metrics.reporting.CsvReporter$1.getStream(CsvReporter.java:161)
at
com.yammer.metrics.reporting.CsvReporter.processGauge(CsvReporter.java:239)
at
com.yammer.metrics.reporting.CsvReporter.processGauge(CsvReporter.java:24)
at
com.yammer.metrics.reporting.MetricDispatcher.dispatch(MetricDispatcher.java:8)
at com.yammer.metrics.reporting.CsvReporter.run(CsvReporter.java:168)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Reporter: Neha Narkhede
Priority: Critical
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
