Skip to content

Issue with CloudDataFusionStartPipelineOperator  #10030

Closed

Description

@akspow

I am using the CloudDataFusionStartPipelineOperator in Google cloud composer and success_states = ["COMPLETED"] parameter to wait for the pipeline to be successful. It works fine, but sometimes I receive this error:

[2020-07-28 08:16:46,390] {taskinstance.py:1059} ERROR - Retrieving a pipeline state failed with code 404
Traceback (most recent call last)
  File "/usr/local/lib/airflow/airflow/models/taskinstance.py", line 930, in _run_raw_tas
    result = task_copy.execute(context=context
  File "/usr/local/lib/airflow/airflow/providers/google/cloud/operators/datafusion.py", line 700, in execut
    runtime_args=self.runtime_args
  File "/usr/local/lib/airflow/airflow/providers/google/cloud/hooks/datafusion.py", line 498, in start_pipelin
    instance_url=instance_url
  File "/usr/local/lib/airflow/airflow/providers/google/cloud/hooks/datafusion.py", line 114, in wait_for_pipeline_stat
    namespace=namespace
  File "/usr/local/lib/airflow/airflow/providers/google/cloud/hooks/datafusion.py", line 442, in _get_workflow_stat
    f"Retrieving a pipeline state failed with code {response.status}
airflow.exceptions.AirflowException: Retrieving a pipeline state failed with code 404

But the Datafusion pipeline gets completed successfully.
It would be helpful if someone resolves this.

Activity

  1. boring-cyborg commented on Jul 28, 2020

    @boring-cyborg

    Thanks for opening your first issue here! Be sure to follow the issue template!

  2. added a commit that references this issue on Jul 28, 2020
    9122780
  3. turbaszek commented on Jul 28, 2020

    @turbaszek
    Member

    Thanks for reporting @akspow ! I think this may be related to the fact that DataFusion happens to have some lags (I experienced it when writing those operators, see the example DAG where we use dummy operator with sleep)

  4. akspow commented on Jul 29, 2020

    @akspow
    Author

    Is there a quick fix for this?

  5. turbaszek commented on Jul 29, 2020

    @turbaszek
    Member

    You can create custom operator using the logic from the existing one and add the change from #10031

  6. added a commit that references this issue on Aug 3, 2020
    27020f8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions