You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/04 19:20:00 UTC
[jira] [Work logged] (BEAM-7348) Option to expire SDK worker
environments
[ https://issues.apache.org/jira/browse/BEAM-7348?focusedWorklogId=253963&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253963 ]
ASF GitHub Bot logged work on BEAM-7348:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/19 19:19
Start Date: 04/Jun/19 19:19
Worklog Time Spent: 10m
Work Description: mxm commented on pull request #8714: [BEAM-7348] Support environment expiration
URL: https://github.com/apache/beam/pull/8714
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 253963)
Time Spent: 2h 40m (was: 2.5h)
> Option to expire SDK worker environments
> ----------------------------------------
>
> Key: BEAM-7348
> URL: https://issues.apache.org/jira/browse/BEAM-7348
> Project: Beam
> Issue Type: Improvement
> Components: runner-core
> Affects Versions: 2.12.0
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: portability, portability-flink
> Fix For: 2.14.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> We discovered that Python SDK workers are susceptible to memory leaks that are quite hard to identify and/or fix. This becomes an issue in streaming pipelines, where the workers run "forever". It would be good if the user has an option to recycle the workers when there is no other practical way to address (slow) resource leaks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)