[jira] [Commented] (BEAM-10291) Lull detection log to include full thread dump

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177905#comment-17177905 ] 

Beam JIRA Bot commented on BEAM-10291:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>              Labels: stale-assigned
>          Time Spent: 6h 10m
>  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)