[
https://issues.apache.org/jira/browse/BEAM-9065?focusedWorklogId=368916&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368916
]
ASF GitHub Bot logged work on BEAM-9065:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/20 10:18
Start Date: 09/Jan/20 10:18
Worklog Time Spent: 10m
Work Description: echauchot commented on issue #10530: [BEAM-9065] Reset
MetricsContainerStepMapAccumulator upon initialization of MetricsAccumulator
singleton
URL: https://github.com/apache/beam/pull/10530#issuecomment-572492124
@iemejia waiting on a test in a cluster to see it this fixes the behavior
observed. For now I'm not able to reproduce it in a JUnit test, so the problem
might be else where. Keeping that PR open until the test is done and a proper
Junit is available
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 368916)
Time Spent: 40m (was: 0.5h)
> Spark runner accumulates metrics (incorrectly) between runs
> -----------------------------------------------------------
>
> Key: BEAM-9065
> URL: https://issues.apache.org/jira/browse/BEAM-9065
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When pipeline.run() is called, MetricsAccumulator (wrapper of
> MetricsContainerStepMap spark accumulator) is initialized. Spark needs this
> class to be a singleton for failover. The problem is that when several
> pipelines are run inside the same JVM, the initialization ofÂ
> MetricsAccumulator singleton does not reset the underlying spark accumulatorÂ
> causing metrics to be accumulated between runs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
