You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ryan (Jaemun) Jung (Jira)" <ji...@apache.org> on 2022/01/19 16:23:00 UTC
[jira] [Updated] (BEAM-13691) insufficient error message on Cloud Logging
[ https://issues.apache.org/jira/browse/BEAM-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan (Jaemun) Jung updated BEAM-13691:
--------------------------------------
Description:
While using GCP dataflow, the default compute engine service account(PROJECT_NUMBER-compute@developer.gserviceaccount.com) was accidentally deleted by another user. All the scheduled Dataflow jobs suddenly started failing.
But with Cloud Logging messages, it's not possible to figure out the reason because the error message on Cloud Logging only shows general error messages:
```
apache_beam.runners.dataflow.dataflow_runner.DataflowRuntimeException: Dataflow pipeline failed. State: FAILED, Error:
Error processing pipeline.
```
While the logs in the internal logging system clearly indicates as:`not_found: Account deleted`
If it's possible to offer detailed information via Cloud Logging, it will allows the users to troubleshoot a lot more easily.
Please let me know if there's any further information needed.
(Creating a Beam issue because I was guided it's a Beam feature rather than a Dataflow)
was:
While using GCP dataflow, the default compute engine service account(PROJECT_NUMBER-compute@developer.gserviceaccount.com) was accidentally deleted by another user. All the scheduled Dataflow jobs suddenly started failing.
But with Cloud Logging messages, it's not possible to figure out the reason because the error message on Cloud Logging only shows general error messages:
```
apache_beam.runners.dataflow.dataflow_runner.DataflowRuntimeException: Dataflow pipeline failed. State: FAILED, Error:
Error processing pipeline.
```
While the logs in the internal logging system clearly indicates as:`not_found: Account deleted`
If it's possible to offer detailed information via Cloud Logging, it allows the users to troubleshoot a lot more easily.
Please let me know if there's any further information needed.
(Creating a Beam issue because I was guided it's a Beam feature rather than a Dataflow)
> insufficient error message on Cloud Logging
> -------------------------------------------
>
> Key: BEAM-13691
> URL: https://issues.apache.org/jira/browse/BEAM-13691
> Project: Beam
> Issue Type: New Feature
> Components: runner-dataflow
> Reporter: Ryan (Jaemun) Jung
> Priority: P2
>
> While using GCP dataflow, the default compute engine service account(PROJECT_NUMBER-compute@developer.gserviceaccount.com) was accidentally deleted by another user. All the scheduled Dataflow jobs suddenly started failing.
> But with Cloud Logging messages, it's not possible to figure out the reason because the error message on Cloud Logging only shows general error messages:
> ```
> apache_beam.runners.dataflow.dataflow_runner.DataflowRuntimeException: Dataflow pipeline failed. State: FAILED, Error:
> Error processing pipeline.
> ```
> While the logs in the internal logging system clearly indicates as:`not_found: Account deleted`
> If it's possible to offer detailed information via Cloud Logging, it will allows the users to troubleshoot a lot more easily.
> Please let me know if there's any further information needed.
> (Creating a Beam issue because I was guided it's a Beam feature rather than a Dataflow)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)