Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2428
---
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 enab
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55978105
Ok, thanks I'm merging this into master and 1.1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55977471
I've already investigated other Backends but I think this issue is occurred
only in SparkDeploySchedulerBackend.
---
If your project is set up for it, you can reply to t
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55976928
Looks good. Have you looked at whether we need to do the same for other
scheduler backends? (e.g. yarn, mesos)
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55881519
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20465/consoleFull)
for PR 2428 at commit
[`c7d890d`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55875701
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20465/consoleFull)
for PR 2428 at commit
[`c7d890d`](https://github.com/ap
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2428
[SPARK-3567] appId field in SparkDeploySchedulerBackend should be volatile
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark appid-v
