[
https://issues.apache.org/jira/browse/BEAM-10291?focusedWorklogId=450176&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-450176
]
ASF GitHub Bot logged work on BEAM-10291:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jun/20 01:20
Start Date: 24/Jun/20 01:20
Worklog Time Spent: 10m
Work Description: tvalentyn commented on pull request #12047:
URL: https://github.com/apache/beam/pull/12047#issuecomment-648526151
Sometimes Jenkins has glitches... not sure what is wrong in this case.
Thank you, tests would be helpful since postcommit tests will probably not
exercise this codepath, since it requires a lull to happen. So if somebody adds
a typo in that code, it may go undetected until we have to debug a slow
customer job.
----------------------------------------------------------------
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: 450176)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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)
