[ 
https://issues.apache.org/jira/browse/FLINK-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672758#comment-16672758
 ] 

ASF GitHub Bot commented on FLINK-10715:
----------------------------------------

kl0u commented on issue #6996: [FLINK-10715] Change reporter log level
URL: https://github.com/apache/flink/pull/6996#issuecomment-435306788
 
 
   @zentol I see. So essentially we do not solve the issue but we just 
temporarily make the test pass until the real issue is resolved? In this case, 
I would say we should create subtasks on the issue that explain what are the 
steps taken. 
   
   If this gets merged, the JIRA will be closed and we also never see the issue 
again because we "fixed it" in the test. This means that next time we see the 
issue, it will be a user reporting it. Which is not good.
   
   Also this will be misleading because if someone searches the JIRA, he/she 
will think that the issue is resolved.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> E2e tests fail with ConcurrentModificationException in MetricRegistryImpl
> -------------------------------------------------------------------------
>
>                 Key: FLINK-10715
>                 URL: https://issues.apache.org/jira/browse/FLINK-10715
>             Project: Flink
>          Issue Type: Bug
>          Components: E2E Tests, Metrics
>    Affects Versions: 1.7.0
>            Reporter: Dawid Wysakowicz
>            Assignee: Igal Shilman
>            Priority: Blocker
>              Labels: pull-request-available
>
> Couple of e2e tests that rely on metrics fail with exception:
> {code}
> 2018-10-29 11:40:32,781 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:101)
>       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}
> Tests that failed:
> *  'Resuming Externalized Checkpoint (file, sync, no parallelism change) 
> end-to-end test
> * 'State TTL Heap backend end-to-end test'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to