[
https://issues.apache.org/jira/browse/FLINK-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569945#comment-16569945
]
Stephan Ewen commented on FLINK-10035:
--------------------------------------
If something is not a problem, it should not be as a warning in the log.
Any ERROR or WARN in the log raises alarm bells for users and causes them to
hesitate to trust the implementation. If this is really not a problem, let's
remove the logging statement.
> ConcurrentModificationException with flink-metrics-slf4j
> --------------------------------------------------------
>
> Key: FLINK-10035
> URL: https://issues.apache.org/jira/browse/FLINK-10035
> Project: Flink
> Issue Type: Bug
> Components: Metrics
> Affects Versions: 1.5.2
> Reporter: Nico Kruber
> Priority: Major
>
> {code}
> 2018-08-02 15:45:08,052 WARN
> org.apache.flink.runtime.metrics.MetricRegistryImpl - Error while
> reporting metrics
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1471)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1469)
> at
> org.apache.flink.metrics.slf4j.Slf4jReporter.report(Slf4jReporter.java:95)
> at
> org.apache.flink.runtime.metrics.MetricRegistryImpl$ReporterTask.run(MetricRegistryImpl.java:427)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> https://api.travis-ci.org/v3/job/411307171/log.txt
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
