You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ning (Jira)" <ji...@apache.org> on 2022/03/04 19:07:00 UTC
[jira] [Commented] (BEAM-13691) insufficient error message on Cloud Logging
[ https://issues.apache.org/jira/browse/BEAM-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501482#comment-17501482 ]
Ning commented on BEAM-13691:
-----------------------------
Talked with Udi. I'll work on an one-pager to propose a solution.
> insufficient error message on Cloud Logging
> -------------------------------------------
>
> Key: BEAM-13691
> URL: https://issues.apache.org/jira/browse/BEAM-13691
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Ryan (Jaemun) Jung
> Assignee: Ning
> Priority: P2
> Labels: error_message_improvement, usability
>
> 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 allow the users to troubleshoot by themselves.
> Please let me know if there's any further information needed.
> (Creating a Beam ticket because I was guided that it's a Beam related feature than Dataflow)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)