[
https://issues.apache.org/jira/browse/BEAM-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531321#comment-17531321
]
Beam JIRA Bot commented on BEAM-13718:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> MemoryMonitor only uploads to GCS on restart
> --------------------------------------------
>
> Key: BEAM-13718
> URL: https://issues.apache.org/jira/browse/BEAM-13718
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-harness
> Reporter: Lara Schmidt
> Priority: P2
> Labels: stale-P2
>
> The current MemoryMonitor has an option to upload a profile to GCS. However
> it only uploads the profile to GCS when starting the memory monitor thread.
> This is currently done when the harness is started only.
> However MemoryMonitor's tryToDumpHeap is public and therefore can be called
> clients at any point (e.g. not only on worker restart). In this case we do
> not upload to GCS until the harness restarts which is not good end user
> behavior. It's currently called by StreamingDataflowWorker at a point of high
> memory but before the worker will actually crash, which is how we caught this
> behavior.
> Probably we should add a boolean to tryToHeapDump to get an idea for if the
> worker is about to die or if this is a pre-emptive dump. If it's pre-emptive
> we can probably immediately upload it to GCS as well if so configured.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
