[
https://issues.apache.org/jira/browse/BEAM-14144?focusedWorklogId=746916&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-746916
]
ASF GitHub Bot logged work on BEAM-14144:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Mar/22 01:12
Start Date: 24/Mar/22 01:12
Worklog Time Spent: 10m
Work Description: steveniemitz commented on pull request #17151:
URL: https://github.com/apache/beam/pull/17151#issuecomment-1076969932
I think I lost the LOG line that logs the uploaded path at some point when I
was cherry-picking this, lemme add that back.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 746916)
Time Spent: 1h 40m (was: 1.5h)
> Record JFR profiles when GC thrashing is detected
> -------------------------------------------------
>
> Key: BEAM-14144
> URL: https://issues.apache.org/jira/browse/BEAM-14144
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
> Priority: P2
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> It'd be useful for debugging GC issues in jobs to have allocation profiles
> when it was occurring. In java 9+, JFR is included in the JDK, we could use
> that to record profiles when GC thrashing is detected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
