spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bbejeck <>
Subject [GitHub] spark pull request: [CORE] SPARK-3178 setting SPARK_WORKER_MEMORY ...
Date Mon, 01 Sep 2014 11:57:06 GMT
GitHub user bbejeck opened a pull request:

    [CORE] SPARK-3178 setting SPARK_WORKER_MEMORY to a value without a label (m or g) sets
the worker memory limit to zero

    Now the worker will fail fast if the memory is set to zero by leaving off the the label
(m or g) either in the SPARK_WORKER_MEMORY environment variable or from the command line.

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

    $ git pull master

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 #2227
commit 8abf665afef9b76e9886e72e596e687bd7516475
Author: Bill Bejeck <>
Date:   2014-09-01T02:54:29Z

    SPARK-3178 - Validate the memory is greater than zero when set from the SPARK_WORKER_MEMORY
environment variable or command line without a g or m label.  Added unit tests. If memory
is 0 an IllegalStateException is thrown.

commit e9bcf2cf6fe5b3aa1649c80c82f8ff240662f413
Author: Bill Bejeck <>
Date:   2014-09-01T02:57:56Z

    Merge remote-tracking branch 'upstream/master'
    Merging updates from Spark upstream on 8/31/14


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message