You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/03/30 16:57:41 UTC

[jira] [Updated] (BEAM-1594) Treat JOB_STATE_DRAINED as terminal in DataflowRunner

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

Daniel Halperin updated BEAM-1594:
----------------------------------
    Summary: Treat JOB_STATE_DRAINED as terminal in DataflowRunner  (was: JOB_STATE_DRAINED should be terminal for waitUntilFinish())

> Treat JOB_STATE_DRAINED as terminal in DataflowRunner
> -----------------------------------------------------
>
>                 Key: BEAM-1594
>                 URL: https://issues.apache.org/jira/browse/BEAM-1594
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Eugene Kirpichov
>            Assignee: Eugene Kirpichov
>             Fix For: First stable release
>
>
> Dataflow runner supports pipeline draining for streaming pipelines, which stops consuming input and waits for all watermarks to progress to infinity and then declares the pipeline complete. When watermarks progress to infinity after a drain request, the Dataflow runner will mark the job DRAINED (In the future, when watermarks progress to infinity without a drain request, it will mark the job DONE instead). JOB_STATE_DRAINED is logically a terminal state - no more data will be processed and the pipeline's resources are torn down - and waitUntilFinish() should terminate if the job enters this state.



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