You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/21 17:07:01 UTC
[jira] [Assigned] (BEAM-10291) Lull detection log to include full
thread dump
[ https://issues.apache.org/jira/browse/BEAM-10291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot reassigned BEAM-10291:
------------------------------------
Assignee: (was: David Yan)
> 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
> 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)