You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:04 UTC

[jira] [Updated] (BEAM-12751) Python DataflowRunner doesn't set client_request_id

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

Kenneth Knowles updated BEAM-12751:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Python DataflowRunner doesn't set client_request_id
> ---------------------------------------------------
>
>                 Key: BEAM-12751
>                 URL: https://issues.apache.org/jira/browse/BEAM-12751
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-py-core
>         Environment: python
>            Reporter: Minbo Bae
>            Priority: P3
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Currently,  [Java DataflowRunner|https://github.com/apache/beam/blob/v2.28.0/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/DataflowRunner.java#L999] sets {{clientRequestId}}, but [Python DataflowRunner|https://github.com/apache/beam/blob/v2.31.0/sdks/python/apache_beam/runners/dataflow/dataflow_runner.py] has no such logic.
> This causes an issue with job creation when the first try is failed with DEADLINE_EXCEEDED (but actually job successfully created), because the second try will fail with "There is already an active job named...".  As per [Dataflow public doc|https://cloud.google.com/dataflow/docs/reference/rest/v1b3/projects.locations.jobs], `clientRequestId` must be set to avoid this issue.
> In addition, as the retry happens in  [google-apitools|https://github.com/google/apitools/blob/v0.5.31/apitools/base/py/http_wrapper.py#L346-L360] and it doesn't print any logs, the error message is difficult to understand and there is actually a successfully created job even if it returns the error.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)