You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by pankajarora12 <gi...@git.apache.org> on 2015/04/13 18:44:05 UTC

[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

GitHub user pankajarora12 opened a pull request:

    https://github.com/apache/spark/pull/5494

    [CORE] SPARK-6880: Fixed null check when all the dependent stages are cancelled due to previous stage failure

    Fixed null check when all the dependent stages are cancelled due to previous stage failure. This happens when one of the executor node goes down and all the dependent stages are cancelled.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pankajarora12/spark NEWBRANCH

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/5494.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 #5494
    
----
commit 457572018f154399e4f36b8cec8089010faeedc9
Author: pankaj arora <pa...@guavus.com>
Date:   2015-04-13T16:27:58Z

    [CORE] SPARK-6880: Fixed null check when all the dependent stages are cancelled due to previous stage failure

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by pankajarora12 <gi...@git.apache.org>.
Github user pankajarora12 commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5494#discussion_r28257067
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala ---
    @@ -818,13 +818,12 @@ class DAGScheduler(
           }
         }
     
    -    val properties = if (jobIdToActiveJob.contains(jobId)) {
    -      jobIdToActiveJob(stage.jobId).properties
    -    } else {
    -      // this stage will be assigned to "default" pool
    -      null
    +    val activeJob = jobIdToActiveJob.get(stage.jobId).getOrElse(null)
    --- End diff --
    
    Yeah this one liner should work.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by srowen <gi...@git.apache.org>.
Github user srowen commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5494#discussion_r28256591
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala ---
    @@ -818,13 +818,12 @@ class DAGScheduler(
           }
         }
     
    -    val properties = if (jobIdToActiveJob.contains(jobId)) {
    -      jobIdToActiveJob(stage.jobId).properties
    -    } else {
    -      // this stage will be assigned to "default" pool
    -      null
    +    val activeJob = jobIdToActiveJob.get(stage.jobId).getOrElse(null)
    --- End diff --
    
    Are you suggesting that in some cases `jobId != stage.jobId` and that's the error?
    Then just `val properties = jobIdToActiveJob.get(stage.jobId).map(_.properties).getOrElse(null)`?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-92950561
  
    Test PASSed.
    Refer to this link for build results (access rights to CI server needed): 
    https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30246/
    Test PASSed.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-92889845
  
      [Test build #30246 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30246/consoleFull) for   PR 5494 at commit [`55ba5e3`](https://github.com/apache/spark/commit/55ba5e350fc922696342aa38b99ad0bdfad64f92).


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by pankajarora12 <gi...@git.apache.org>.
Github user pankajarora12 commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5494#discussion_r28330542
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala ---
    @@ -818,13 +818,12 @@ class DAGScheduler(
           }
         }
     
    -    val properties = if (jobIdToActiveJob.contains(jobId)) {
    -      jobIdToActiveJob(stage.jobId).properties
    -    } else {
    -      // this stage will be assigned to "default" pool
    -      null
    +    val activeJob = jobIdToActiveJob.get(stage.jobId).getOrElse(null)
    --- End diff --
    
    Commited new change.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/spark/pull/5494


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by srowen <gi...@git.apache.org>.
Github user srowen commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-92888003
  
    ok to test


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-92422400
  
    Can one of the admins verify this patch?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by srowen <gi...@git.apache.org>.
Github user srowen commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5494#discussion_r28319112
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala ---
    @@ -818,13 +818,12 @@ class DAGScheduler(
           }
         }
     
    -    val properties = if (jobIdToActiveJob.contains(jobId)) {
    -      jobIdToActiveJob(stage.jobId).properties
    -    } else {
    -      // this stage will be assigned to "default" pool
    -      null
    +    val activeJob = jobIdToActiveJob.get(stage.jobId).getOrElse(null)
    --- End diff --
    
    Just push a change to this same branch that overwrites with the new change. Then it can be tested.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by andrewor14 <gi...@git.apache.org>.
Github user andrewor14 commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5494#discussion_r28359183
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala ---
    @@ -818,12 +818,7 @@ class DAGScheduler(
           }
         }
     
    -    val properties = if (jobIdToActiveJob.contains(jobId)) {
    -      jobIdToActiveJob(stage.jobId).properties
    -    } else {
    -      // this stage will be assigned to "default" pool
    -      null
    -    }
    +    val properties = jobIdToActiveJob.get(stage.jobId).map(_.properties).getOrElse(null)    
    --- End diff --
    
    could be `orNull`, not a big deal at all


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-92950455
  
      [Test build #30246 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30246/consoleFull) for   PR 5494 at commit [`55ba5e3`](https://github.com/apache/spark/commit/55ba5e350fc922696342aa38b99ad0bdfad64f92).
     * This patch **passes all tests**.
     * This patch merges cleanly.
     * This patch adds no public classes.
     * This patch does not change any dependencies.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [CORE] SPARK-6880: Fixed null check when all t...

Posted by andrewor14 <gi...@git.apache.org>.
Github user andrewor14 commented on the pull request:

    https://github.com/apache/spark/pull/5494#issuecomment-93021950
  
    Thanks I'm merging this into master.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org