[
https://issues.apache.org/jira/browse/BEAM-6018?focusedWorklogId=167995&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-167995
]
ASF GitHub Bot logged work on BEAM-6018:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Nov/18 21:58
Start Date: 20/Nov/18 21:58
Worklog Time Spent: 10m
Work Description: udim commented on issue #6994: [BEAM-6018] Fix slow
memory leak in GcsUtil
URL: https://github.com/apache/beam/pull/6994#issuecomment-440444219
@pabloem If the pipeline has on the order of 1e4 or 1e5 output files *per
worker* in GCS it might trigger this leak.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 167995)
Time Spent: 1h 50m (was: 1h 40m)
> Memory leak in GCSUtil.java executeBatches
> ------------------------------------------
>
> Key: BEAM-6018
> URL: https://issues.apache.org/jira/browse/BEAM-6018
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.7.0
> Reporter: Udi Meiri
> Assignee: Udi Meiri
> Priority: Major
> Fix For: 2.9.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In streaming pipelines there are multiple calls to moveToOutputFiles
> (https://github.com/apache/beam/blob/42984a821b3e73aee2966d11d7fb436b5ff22b68/sdks/java/core/src/main/java/org/apache/beam/sdk/io/WriteFiles.java#L796).
> When writing to GCS, this call uses executeBatches
> (https://github.com/apache/beam/blob/279a05604b83a54e8e5a79e13d8761f94841f326/sdks/java/extensions/google-cloud-platform-core/src/main/java/org/apache/beam/sdk/util/GcsUtil.java#L551),
> which wraps a thread pool in MoreExecutors.getExitingExecutorService(). This
> wrapper introduces a DelayedShutdownHook which persists until the worker
> exits.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
