GitHub user devaraj-kavali opened a pull request:
https://github.com/apache/spark/pull/12571
[SPARK-1989] [CORE] Exit executors faster if they get into a cycle of heavy
GC
## What changes were proposed in this pull request?
Added spark.executor.gcTimeLimit config for getting the value for the GC
Option -XX:GCTimeLimit and spark.executor.gcHeapFreeLimit config for getting
the value for the GC Option -XX:GCHeapFreeLimit. Now GC time limit and heap
free limit options need to set using these configs and are not allowed as part
of spark.executor.extraJavaOptions.
## How was this patch tested?
I have verified this by checking the executor process command when I ran
different spark applications. I verified the same in different deployement
modes(Standalone, YARN, Mesos).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/devaraj-kavali/spark SPARK-1989
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12571.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #12571
----
commit 4f715623487f95a71b6c38c2e50c5e1b6ec7a1b3
Author: Devaraj K <[email protected]>
Date: 2016-04-21T09:15:07Z
[SPARK-1989] [CORE] Exit executors faster if they get into a cycle of
heavy GC
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
