Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-124298551
@SaintBacchus not so far , any idea for this ?
---
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
Github user xuchenCN closed the pull request at:
https://github.com/apache/spark/pull/7128
---
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
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7107#issuecomment-122153483
+1 LGTM
---
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
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/4380#issuecomment-121565650
LGTM @scwf could you let the 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
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7128#issuecomment-121499587
@andrewor14 All right close this PR
---
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
Github user xuchenCN commented on a diff in the pull request:
https://github.com/apache/spark/pull/7107#discussion_r34648531
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -394,6 +394,27 @@ class
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-120891504
Hi @darkcrawler01 I see the log and this patch looks good to you
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-121137474
I follow the code maybe is lazy declare actorRef value ? and akka internal
problem?
---
If your project is set up for it, you can reply to this email and have your
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-121117560
@darkcrawler01 I mean this pull request will fix your issue
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-120793051
Hi @darkcrawler01
Could you provide detail log?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-117052889
Finally build success , thanks @JoshRosen care for this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user xuchenCN closed the pull request at:
https://github.com/apache/spark/pull/7083
---
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
GitHub user xuchenCN opened a pull request:
https://github.com/apache/spark/pull/7128
[SPARK-8374] [YARN] Job frequently hangs after YARN preemption
Issue description
[SPARK-8374](https://issues.apache.org/jira/browse/SPARK-8374)
Application starve because YARN scheduler
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7083#issuecomment-117213630
PR changes
[https://github.com/apache/spark/pull/7128](https://github.com/apache/spark/pull/7128)
---
If your project is set up for it, you can reply to this email
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7128#issuecomment-117213892
CC @sryza
---
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
GitHub user xuchenCN opened a pull request:
https://github.com/apache/spark/pull/7083
SPARK-8374] [YARN] Job frequently hangs after YARN preemption
Issue description
[SPARK-8374](https://issues.apache.org/jira/browse/SPARK-8374)
Application starve because YARN scheduler
GitHub user xuchenCN opened a pull request:
https://github.com/apache/spark/pull/7077
[SPARK-8592] [CORE] CoarseGrainedExecutorBackend: Cannot register with
driver = NPE
Look detail of this issue at
[SPARK-8592](https://issues.apache.org/jira/browse/SPARK-8592
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7083#issuecomment-116926849
Thanks @sryza I notice that is mistake, I 'm trying to find way to fix
this issue
---
If your project is set up for it, you can reply to this email and have your
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116934136
PR changes to
[https://github.com/apache/spark/pull/7110](https://github.com/apache/spark/pull/7110)
---
If your project is set up for it, you can reply to this email
GitHub user xuchenCN opened a pull request:
https://github.com/apache/spark/pull/7110
[SPARK-8592] [CORE] CoarseGrainedExecutorBackend: Cannot register with
driver = NPE
Look detail of this issue at
[SPARK-8592](https://issues.apache.org/jira/browse/SPARK-8592
Github user xuchenCN closed the pull request at:
https://github.com/apache/spark/pull/7077
---
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
Github user xuchenCN commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116932736
Have no idea for this test ,so I will pull request from master branch
---
If your project is set up for it, you can reply to this email and have your
reply appear
22 matches
Mail list logo
