[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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-volatile-modification Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/2428.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 #2428 commit c7d890d1557254ff7ea01263a6512a3d846d4270 Author: Kousuke Saruta saru...@oss.nttdata.co.jp Date: 2014-09-17T10:19:30Z Added volatile modifier to appId field in SparkDeploySchedulerBackend --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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/apache/spark/commit/c7d890d1557254ff7ea01263a6512a3d846d4270). * This patch merges cleanly. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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/apache/spark/commit/c7d890d1557254ff7ea01263a6512a3d846d4270). * This patch **passes** unit tests. * This patch merges cleanly. * This patch adds no public classes. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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 your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-3567] appId field in SparkDeploySchedul...
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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
