[
https://issues.apache.org/jira/browse/BEAM-10291?focusedWorklogId=450173&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-450173
]
ASF GitHub Bot logged work on BEAM-10291:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jun/20 01:05
Start Date: 24/Jun/20 01:05
Worklog Time Spent: 10m
Work Description: davidyan74 commented on pull request #12047:
URL: https://github.com/apache/beam/pull/12047#issuecomment-648522058
The original lull logging code does not have test coverage. I'll look into
adding tests that cover both the original code and the added code in this PR.
It will take me a while though.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 450173)
Time Spent: 40m (was: 0.5h)
> Lull detection log to include full thread dump
> ----------------------------------------------
>
> Key: BEAM-10291
> URL: https://issues.apache.org/jira/browse/BEAM-10291
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: David Yan
> Assignee: David Yan
> Priority: P2
> Time Spent: 40m
> Remaining Estimate: 0h
>
> What we have today is a thread dump of the thread that's stuck, but in many
> cases (most notably BQ) I/O happens in a separate thread that is not included
> in the dump. Ideally, we'd need to have a full thread dump of the entire
> process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
