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

Posted to issues@beam.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2019/08/12 12:08:00 UTC

[jira] [Updated] (BEAM-7945) Allow runner to configure "semi_persist_dir" which is used in the SDK harness

     [ https://issues.apache.org/jira/browse/BEAM-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sunjincheng updated BEAM-7945:
------------------------------
    Fix Version/s: 2.15.0

> Allow runner to configure "semi_persist_dir" which is used in the SDK harness
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-7945
>                 URL: https://issues.apache.org/jira/browse/BEAM-7945
>             Project: Beam
>          Issue Type: Sub-task
>          Components: java-fn-execution, sdk-go, sdk-java-core, sdk-py-core
>            Reporter: sunjincheng
>            Assignee: sunjincheng
>            Priority: Major
>             Fix For: 2.15.0
>
>
> Currently "semi_persist_dir" is not configurable. This may become a problem in certain scenarios. For example, the default value of "semi_persist_dir" is "/tmp" ([https://github.com/apache/beam/blob/master/sdks/python/container/boot.go#L48]) in Python SDK harness. When the environment type is "PROCESS", the disk of "/tmp" may be filled up and unexpected issues will occur in production environment. We should provide a way to configure "semi_persist_dir" in EnvironmentFactory at the runner side. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)