Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8828
---
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/8828#issuecomment-142453169
Alright, merging into master 1.5. Thanks everyone.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142306215
That is much better, it reports completed times and duration for the entire
application those tasks show up as failed with comment: TaskCommitDenied
(Driver denied tas
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142105765
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142105762
Merged build finished. 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142105606
[Test build #42760 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42760/console)
for PR 8828 at commit
[`b89eb37`](https://github.
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142103825
yes it only happens with speculation. I'll try it out.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142101324
Yes I believe so. @tgravescs can you give it another try?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142066981
The approach looks ok to me if it works (seems this only affects jobs with
speculative execution on?).
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142064037
[Test build #42760 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42760/consoleFull)
for PR 8828 at commit
[`b89eb37`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142062406
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-142062384
Merged build triggered.
---
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 h
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141661904
Also since those values are missing it also causes duration and completed
time to not show up. Makes it difficult for users to debug there job. This
particular job I
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141632266
Hm, unfortunately it appears that we missed two whole minor versions (1.3.0
and 1.4.0). I wonder if we should add some backward compatible handling for
those versions
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141599896
ok it finally loaded. So the history UI for that task reports its still
RUNNING since it got the error parsing it. I guess that is ok. Ideally it
would still show en
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141599432
Yeah and actually I want to do one more verification to make sure the rest
of the history file is useful. Unfortunately my network connection is slow
that its a huge
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141597635
[Test build #42703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42703/consoleFull)
for PR 8828 at commit
[`29001f9`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141596522
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141596533
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141593434
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141593394
[Test build #42690 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42690/console)
for PR 8828 at commit
[`f144147`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141593432
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141588955
I see, because in your event log we only logged the name `TaskCommitDenied`
but not the job ID and other details. That makes sense.
---
If your project is set up for
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141587727
+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
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141586772
well your change fixes that error and it now displays the file on the
screen. But it does throw an exception. I think its due to the missing fields
in the history file
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141575063
Great, thanks Tom.
---
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
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141570131
thanks, hadn't had a chance to finish this. I'll try out your changes on my
bad history file to make sure it works.
---
If your project is set up for it, you can repl
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141568727
[Test build #42690 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42690/consoleFull)
for PR 8828 at commit
[`f144147`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141567383
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141567360
Merged build triggered.
---
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 h
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/8828
[SPARK-10640] History server fails to parse TaskCommitDenied
... simply because the code is missing!
You can merge this pull request into a Git repository by running:
$ git pull https://gith
31 matches
Mail list logo
