You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/02/21 22:57:00 UTC

[jira] [Comment Edited] (BEAM-3700) PipelineOptionsFactory leaks memory

    [ https://issues.apache.org/jira/browse/BEAM-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372153#comment-16372153 ] 

Luke Cwik edited comment on BEAM-3700 at 2/21/18 10:56 PM:
-----------------------------------------------------------

As the follow up to [https://github.com/apache/beam/pull/4674,] please consider making PipelineOptionsFactory an instance variable instead of a Cache that is contained within.

 

This will help protect users from cache reset thread safety issues.


was (Author: lcwik):
As the follow up to [https://github.com/apache/beam/pull/4674,] please consider making PipelineOptionsFactory an instance variable instead of a Cache that is contained within.

> PipelineOptionsFactory leaks memory
> -----------------------------------
>
>                 Key: BEAM-3700
>                 URL: https://issues.apache.org/jira/browse/BEAM-3700
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-java-core
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>            Priority: Major
>             Fix For: 2.4.0
>
>
> PipelineOptionsFactory has a lot of cache but no way to reset it. This task is about adding a public method to be able to control it in integrations (runners likely).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)