Uh oh!
There was an error while loading. Please reload this page.
[SPARK-1953][YARN]yarn client mode Application Master memory size is same as driver memory... - #3607
[SPARK-1953][YARN]yarn client mode Application Master memory size is same as driver memory...#3607WangTaoTheTonic wants to merge 20 commits into
Conversation
WangTaoTheTonic
commented
Dec 4, 2014
SparkQA
commented
Dec 4, 2014
Test build #24141 has started for PR 3607 at commit
|
There was a problem hiding this comment.
env variables are only for backwards compatibility we shouldn't add them for new configs so can you please remove it.
SparkQA
commented
Dec 4, 2014
Test build #24141 has finished for PR 3607 at commit
|
AmplabJenkins
commented
Dec 4, 2014
Test PASSed. |
There was a problem hiding this comment.
I am a little bit on the fence here about having this config in spark-submit. I'm not sure if it will cause more confusion since it only applies to client mode. I'm wondering if perhaps we just add the config for now.
@vanzin@andrewor14 thoughts on that since you both commented on the am.extraJavaOptions pr
There was a problem hiding this comment.
I'd prefer not to add this to SparkSubmit. I've never seen someone have to fiddle with that value, so my guess is that this is such an uncommon need that those who want to use it wouldn't be bothered by the more verbose "--conf" approach.
Also, should probably add a "memory overhead" config too.
AmplabJenkins
commented
Dec 5, 2014
Test FAILed. |
AmplabJenkins
commented
Dec 5, 2014
Test FAILed. |
WangTaoTheTonic
commented
Dec 5, 2014
Jenkins, test this please. |
AmplabJenkins
commented
Dec 5, 2014
Test FAILed. |
WangTaoTheTonic
commented
Dec 5, 2014
Jenkins, test this please. |
AmplabJenkins
commented
Dec 5, 2014
Test FAILed. |
WangTaoTheTonic
commented
Dec 5, 2014
FATAL: Failed to fetch from https://github.com/apache/spark.git Jenkins went wrong? |
andrewor14
commented
Dec 5, 2014
retest this please. Hey @WangTaoTheTonic can you add |
SparkQA
commented
Dec 5, 2014
Test build #24171 has started for PR 3607 at commit
|
SparkQA
commented
Dec 5, 2014
Test build #24171 has finished for PR 3607 at commit
|
AmplabJenkins
commented
Dec 5, 2014
Test PASSed. |
WangTaoTheTonic
commented
Dec 5, 2014
Now |
There was a problem hiding this comment.
This comment is no longer true
andrewor14
commented
Dec 9, 2014
Hey @WangTaoTheTonic I left a few comments. Also, could you document this? Thanks. |
SparkQA
commented
Dec 9, 2014
Test build #24235 has started for PR 3607 at commit
|
There was a problem hiding this comment.
This warning doesn't make sense. It's a perfectly reasonable thing for YARN users to set the driver memory in client mode.
andrewor14
commented
Jan 7, 2015
Hey @WangTaoTheTonic I believe the latest changes correctly addresses my last concern (that in client mode the |
SparkQA
commented
Jan 8, 2015
Test build #25208 has started for PR 3607 at commit
|
WangTaoTheTonic
commented
Jan 8, 2015
Sorry to produce so much issues in last rebase. I've fixed them and tested again on my cluster. Here is the configuration(with
In cluster mode, it will launch two container: one used 6G, another 2G. In client mode they are 512M and 2G. Then keep spark-defaults.conf unchanged with command: In cluster mode, one used 5G, another 2.25G. In client mode, they are 512M and 2.25G. |
SparkQA
commented
Jan 8, 2015
Test build #25208 has finished for PR 3607 at commit
|
AmplabJenkins
commented
Jan 8, 2015
Test PASSed. |
There was a problem hiding this comment.
The default value of 512 is duplicated here and up there. I would do this instead
sparkConf.getOption(amMemKey)
.map(Utils.memoryStringToMb)
.foreach { mem => amMemory = mem }
andrewor14
commented
Jan 8, 2015
Hi @WangTaoTheTonic the latest changes look pretty close. I believe the semantics of what should be set in what mode is as discussed. It would be good if other reviewers can confirm this. By the way you will need to rebase to master because |
There was a problem hiding this comment.
I don't think you want to use println here. Also, I'm always a little conflicted about these logs, since they'll show up when you set these values in the default conf file (which would apply to a lot of different jobs unless they explicitly override the conf file). But not a big deal.
There was a problem hiding this comment.
As ClientArguments.scala didn't extends Logging class, only println can be used here.
Yep, if user set the config values that never be used in that mode, we should give a prompt.
BTW, spark.driver.memory is used in both modes, so I deleted the meesage about it.
SparkQA
commented
Jan 9, 2015
Test build #25284 has started for PR 3607 at commit
|
SparkQA
commented
Jan 9, 2015
Test build #25285 has started for PR 3607 at commit
|
SparkQA
commented
Jan 9, 2015
Test build #25284 has finished for PR 3607 at commit
|
AmplabJenkins
commented
Jan 9, 2015
Test PASSed. |
SparkQA
commented
Jan 9, 2015
Test build #25285 has finished for PR 3607 at commit
|
AmplabJenkins
commented
Jan 9, 2015
Test PASSed. |
There was a problem hiding this comment.
unindent, I will fix when I merge
andrewor14
commented
Jan 9, 2015
Ok I'm merging this into master thanks @WangTaoTheTonic for your repeated updates. |
WangTaoTheTonic
commented
Jan 10, 2015
Oh gosh it is merged finally. |
... size
Ways to set Application Master's memory on yarn-client mode:
spark.yarn.am.memoryin SparkConf or System PropertiesNote: this arguments is only available in yarn-client mode.