beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-3005) Provision API should optionally include SDK harness memory/cpu/disk limits
Date Tue, 24 Oct 2017 04:08:00 GMT


ASF GitHub Bot commented on BEAM-3005:

GitHub user herohde opened a pull request:

    [BEAM-3005] Add resource limits to provisioning

    * Use memory limit for JVM max heap size.

You can merge this pull request into a Git repository by running:

    $ git pull containers

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4029
commit 1514f5a36376c12bef8597b9b37505a01cfec9f7
Author: Henning Rohde <>
Date:   2017-10-20T21:38:54Z

    [BEAM-3005] Add resource limits to provision proto

commit b37e4d1c23b9d7291d8063e525a554ae343fe0ab
Author: Henning Rohde <>
Date:   2017-10-23T16:56:55Z

    [BEAM-3005] Set JVM max heap size in java container

commit 9e8cc1b77e6afbccb181f81db6bc201f40dde68d
Author: Henning Rohde <>
Date:   2017-10-23T16:59:08Z

    Declare .go and Dockerfile as text in gitattributes


> Provision API should optionally include SDK harness memory/cpu/disk limits
> --------------------------------------------------------------------------
>                 Key: BEAM-3005
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Henning Rohde
>            Assignee: Henning Rohde
>            Priority: Minor
>              Labels: portability
> SDK harness containers should be told what resources they can use via the provision API,
notably to configure the JVM heap limit. Disk usage (in the semi-persistent location) and
cpu share can also be added. These limits -- if provided -- may be enforced at the discretion
of the runner (or the reality of the execution environment).

This message was sent by Atlassian JIRA

View raw message