You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/07 15:42:00 UTC

[jira] [Work logged] (BEAM-14175) "Read loop was aborted" errors are very noisy when large jobs fail

     [ https://issues.apache.org/jira/browse/BEAM-14175?focusedWorklogId=754190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-754190 ]

ASF GitHub Bot logged work on BEAM-14175:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Apr/22 15:41
            Start Date: 07/Apr/22 15:41
    Worklog Time Spent: 10m 
      Work Description: lukecwik merged PR #17183:
URL: https://github.com/apache/beam/pull/17183




Issue Time Tracking
-------------------

    Worklog Id:     (was: 754190)
    Time Spent: 20m  (was: 10m)

> "Read loop was aborted" errors are very noisy when large jobs fail
> ------------------------------------------------------------------
>
>                 Key: BEAM-14175
>                 URL: https://issues.apache.org/jira/browse/BEAM-14175
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Steve Niemitz
>            Assignee: Steve Niemitz
>            Priority: P2
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When a large dataflow job fails or is cancelled, "Read loop was aborted." is logged potentially 1000s of times as read operations are interrupted.  These could be instead logged at debug level rather than error to reduce noise in the logs, they often hide actual useful logs.



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