[
https://issues.apache.org/jira/browse/BEAM-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497549#comment-17497549
]
Beam JIRA Bot commented on BEAM-13718:
--------------------------------------
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.
> 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
> Assignee: Kenneth Knowles
> Priority: P2
> Labels: stale-assigned
>
> 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.1#820001)
