You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by trueyao <gi...@git.apache.org> on 2016/03/15 09:36:51 UTC

[GitHub] spark pull request: [SPARK-13901][CORE]correct the logDebug inform...

GitHub user trueyao opened a pull request:

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

    [SPARK-13901][CORE]correct the logDebug information when jump to the next locality level

    JIRA Issue:https://issues.apache.org/jira/browse/SPARK-13901
    In getAllowedLocalityLevel method of TaskSetManager,we get wrong logDebug information when jump to the next locality level.So we should fix it.
    


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

    $ git pull https://github.com/trueyao/spark logDebug-localityWait

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

    https://github.com/apache/spark/pull/11719.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 #11719
    
----
commit a33ad583e92a40cb3b4b59d7fd57584a5e8678e3
Author: trueyao <50...@qq.com>
Date:   2016-03-15T08:06:53Z

    correct the logDebug information when jump to the next locality level

----


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#discussion_r56137442
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
    @@ -557,7 +557,7 @@ private[spark] class TaskSetManager(
             lastLaunchTime += localityWaits(currentLocalityIndex)
             currentLocalityIndex += 1
             logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
    -          s"${localityWaits(currentLocalityIndex)}ms")
    +          s"${localityWaits(currentLocalityIndex - 1)}ms")
    --- End diff --
    
    Pull this out into a `val` above, use it above, and then just reuse it here. It's clearer


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197329002
  
    I'm certain this is an unrelated failure, but not sure why the failure occurs. It has happened on a few builds.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

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


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197226460
  
    **[Test build #53307 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53307/consoleFull)** for PR 11719 at commit [`2eb75cb`](https://github.com/apache/spark/commit/2eb75cbf07106120e1119a45dbb32f00525ad03d).
     * This patch **fails Spark 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 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: [SPARK-13901][CORE]correct the logDebug inform...

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

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


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197215784
  
    **[Test build #53295 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53295/consoleFull)** for PR 11719 at commit [`2eb75cb`](https://github.com/apache/spark/commit/2eb75cbf07106120e1119a45dbb32f00525ad03d).
     * This patch **fails Spark 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 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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#discussion_r56393833
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
    @@ -555,9 +555,9 @@ private[spark] class TaskSetManager(
             // Jump to the next locality level, and reset lastLaunchTime so that the next locality
             // wait timer doesn't immediately expire
             lastLaunchTime += localityWaits(currentLocalityIndex)
    -        currentLocalityIndex += 1
    -        logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
    +        logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex + 1)} after waiting for " +
    --- End diff --
    
    haven't looked closely at this, but could currentLocalityIndex + 1 create an index out of bound for myLocalityLevels?



---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

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


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197195399
  
    Jenkins test this please


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197188375
  
    @srowen  Ready for another look.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-196719618
  
    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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197321496
  
    The error of "java.lang.IllegalArgumentException: requirement failed"  is confusing,I just exchange two lines of codes..Actually am I wrong ?


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#discussion_r56152374
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
    @@ -543,21 +543,22 @@ private[spark] class TaskSetManager(
             case TaskLocality.NO_PREF => pendingTasksWithNoPrefs.nonEmpty
             case TaskLocality.RACK_LOCAL => moreTasksToRunIn(pendingTasksForRack)
           }
    +      val previousLocalityIndex = currentLocalityIndex
           if (!moreTasks) {
             // This is a performance optimization: if there are no more tasks that can
             // be scheduled at a particular locality level, there is no point in waiting
             // for the locality wait timeout (SPARK-4939).
             lastLaunchTime = curTime
    -        logDebug(s"No tasks for locality level ${myLocalityLevels(currentLocalityIndex)}, " +
    -          s"so moving to locality level ${myLocalityLevels(currentLocalityIndex + 1)}")
             currentLocalityIndex += 1
    +        logDebug(s"No tasks for locality level ${myLocalityLevels(previousLocalityIndex)}, " +
    +          s"so moving to locality level ${myLocalityLevels(currentLocalityIndex)}")
           } else if (curTime - lastLaunchTime >= localityWaits(currentLocalityIndex)) {
             // Jump to the next locality level, and reset lastLaunchTime so that the next locality
             // wait timer doesn't immediately expire
             lastLaunchTime += localityWaits(currentLocalityIndex)
             currentLocalityIndex += 1
             logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
    -          s"${localityWaits(currentLocalityIndex)}ms")
    +          s"${localityWaits(previousLocalityIndex)}ms")
    --- End diff --
    
    Oh,I got it ,thank you for help.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197226489
  
    Merged build finished. Test FAILed.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#discussion_r56394190
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
    @@ -555,9 +555,9 @@ private[spark] class TaskSetManager(
             // Jump to the next locality level, and reset lastLaunchTime so that the next locality
             // wait timer doesn't immediately expire
             lastLaunchTime += localityWaits(currentLocalityIndex)
    -        currentLocalityIndex += 1
    -        logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
    +        logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex + 1)} after waiting for " +
    --- End diff --
    
    Before, it was incremented first and then used as an index, and now it's increment afterwards, so it shouldn't be different. Really the net change is for the second part of the message to refer to the _previous_ index, so should be OK.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#discussion_r56150936
  
    --- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
    @@ -543,21 +543,22 @@ private[spark] class TaskSetManager(
             case TaskLocality.NO_PREF => pendingTasksWithNoPrefs.nonEmpty
             case TaskLocality.RACK_LOCAL => moreTasksToRunIn(pendingTasksForRack)
           }
    +      val previousLocalityIndex = currentLocalityIndex
           if (!moreTasks) {
             // This is a performance optimization: if there are no more tasks that can
             // be scheduled at a particular locality level, there is no point in waiting
             // for the locality wait timeout (SPARK-4939).
             lastLaunchTime = curTime
    -        logDebug(s"No tasks for locality level ${myLocalityLevels(currentLocalityIndex)}, " +
    -          s"so moving to locality level ${myLocalityLevels(currentLocalityIndex + 1)}")
             currentLocalityIndex += 1
    +        logDebug(s"No tasks for locality level ${myLocalityLevels(previousLocalityIndex)}, " +
    +          s"so moving to locality level ${myLocalityLevels(currentLocalityIndex)}")
           } else if (curTime - lastLaunchTime >= localityWaits(currentLocalityIndex)) {
             // Jump to the next locality level, and reset lastLaunchTime so that the next locality
             // wait timer doesn't immediately expire
             lastLaunchTime += localityWaits(currentLocalityIndex)
             currentLocalityIndex += 1
             logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +
    -          s"${localityWaits(currentLocalityIndex)}ms")
    +          s"${localityWaits(previousLocalityIndex)}ms")
    --- End diff --
    
    Ah OK, not quite what I meant. But, how about a slightly different idea. To match how the debug statement above works, leave it as-is, but then make this one:
    
    ```
    logDebug(s"Moving to ${myLocalityLevels(currentLocalityIndex)} after waiting for " +		          
      s"${localityWaits(currentLocalityIndex+1)}ms")
    currentLocalityIndex += 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 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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197220789
  
    Jenkins retest this please


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197215910
  
    Merged build finished. Test FAILed.


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-196783948
  
    I'm really sorry to make extra commits...Are these codes clearer ?


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197195652
  
    **[Test build #53295 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53295/consoleFull)** for PR 11719 at commit [`2eb75cb`](https://github.com/apache/spark/commit/2eb75cbf07106120e1119a45dbb32f00525ad03d).


---
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: [SPARK-13901][CORE]correct the logDebug inform...

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

    https://github.com/apache/spark/pull/11719#issuecomment-197221731
  
    **[Test build #53307 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53307/consoleFull)** for PR 11719 at commit [`2eb75cb`](https://github.com/apache/spark/commit/2eb75cbf07106120e1119a45dbb32f00525ad03d).


---
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