You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/07/03 17:21:01 UTC

[jira] [Commented] (BEAM-12447) SdkContainerImageBuilder should take machineType configs

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

Beam JIRA Bot commented on BEAM-12447:
--------------------------------------

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.

> SdkContainerImageBuilder should take machineType configs
> --------------------------------------------------------
>
>                 Key: BEAM-12447
>                 URL: https://issues.apache.org/jira/browse/BEAM-12447
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow, sdk-py-core
>            Reporter: Yichi Zhang
>            Assignee: Yichi Zhang
>            Priority: P2
>              Labels: stale-assigned
>
> When prebuilding the python SDK container harness image with SdkContainerImageBuilder on google cloud build, it can run out of memory and fail the build with docker exit code 137. The default machineType is only n1-standard-1 and it is unlikely sufficient to build large images.
>  
> The SdkContainerImageBuilder should take additional machineType configs to circumvent the docker OOM issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)