diff options
| author | jerryshao <sshao@hortonworks.com> | 2016-03-18 12:39:49 -0700 |
|---|---|---|
| committer | Marcelo Vanzin <vanzin@cloudera.com> | 2016-03-18 12:39:49 -0700 |
| commit | 3537782168aa9278ac4add1a25afac0ec6e17085 (patch) | |
| tree | cb5fcec81608a012b6027e2b3ad25313371f50fc /yarn/pom.xml | |
| parent | 9c23c818ca0175c8f2a4a66eac261ec251d27c97 (diff) | |
| download | spark-3537782168aa9278ac4add1a25afac0ec6e17085.tar.gz spark-3537782168aa9278ac4add1a25afac0ec6e17085.tar.bz2 spark-3537782168aa9278ac4add1a25afac0ec6e17085.zip | |
[SPARK-13885][YARN] Fix attempt id regression for Spark running on Yarn
## What changes were proposed in this pull request?
This regression is introduced in #9182, previously attempt id is simply as counter "1" or "2". With the change of #9182, it is changed to full name as "appattemtp-xxx-00001", this will affect all the parts which uses this attempt id, like event log file name, history server app url link. So here change it back to the counter to keep consistent with previous code.
Also revert back this patch #11518, this patch fix the url link of history log according to the new way of attempt id, since here we change back to the previous way, so this patch is not necessary, here to revert it.
Also clean "spark.yarn.app.id" and "spark.yarn.app.attemptId", since it is useless now.
## How was this patch tested?
Test it with unit test and manually test different scenario:
1. application running in yarn-client mode.
2. application running in yarn-cluster mode.
3. application running in yarn-cluster mode with multiple attempts.
Checked both the event log file name and url link.
CC vanzin tgravescs , please help to review, thanks a lot.
Author: jerryshao <sshao@hortonworks.com>
Closes #11721 from jerryshao/SPARK-13885.
Diffstat (limited to 'yarn/pom.xml')
0 files changed, 0 insertions, 0 deletions