You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2017/05/09 21:31:04 UTC

[jira] [Assigned] (BEAM-2186) Use Accumulable MetricsContainers in the DirectRunner

     [ https://issues.apache.org/jira/browse/BEAM-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Groh reassigned BEAM-2186:
---------------------------------

    Assignee:     (was: Thomas Groh)

> Use Accumulable MetricsContainers in the DirectRunner
> -----------------------------------------------------
>
>                 Key: BEAM-2186
>                 URL: https://issues.apache.org/jira/browse/BEAM-2186
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>            Reporter: Ben Chambers
>
> Once PR 2649 is submitted, we should be able to use the accumulable functionality to clean up the DirectRunner. Since this runner updates metrics from multiple processing threads simultaneously, we will need to figure out how to either (1) make the accumulable behavior thread safe or (2) have a non-blocking way of performing the accumulation sequentially.
> If we go with (2), we can put updated containers in a queue and then have a single thread trying to apply those updates.
> https://github.com/apache/beam/blob/master/runners/direct-java/src/main/java/org/apache/beam/runners/direct/WatermarkManager.java#L912)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)