Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37295276
Build finished.
---
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37295278
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13116/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37290420
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 this feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37290419
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 have this f
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37287900
Sorry for late. There's something wrong with my cluster, and I'm afraid the
code here is not tested right now.
---
If your project is set up for it, you can reply to this ema
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37156504
Sorry, I was a little busy last week. I'll push new version today.
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37156364
Not sure if you saw this, @iven, but Ben put some good comments above --
would be good to fix those.
---
If your project is set up for it, you can reply to this email and h
Github user benh commented on a diff in the pull request:
https://github.com/apache/spark/pull/60#discussion_r10243718
--- Diff: docs/configuration.md ---
@@ -134,6 +134,22 @@ Apart from these, the following properties are also
available, and may be useful
+
Github user benh commented on a diff in the pull request:
https://github.com/apache/spark/pull/60#discussion_r10243692
--- Diff: docs/running-on-mesos.md ---
@@ -15,13 +15,15 @@ Spark can run on clusters managed by [Apache
Mesos](http://mesos.apache.org/). F
* `export MESOS
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/60#discussion_r10243489
--- Diff: docs/running-on-mesos.md ---
@@ -15,13 +15,15 @@ Spark can run on clusters managed by [Apache
Mesos](http://mesos.apache.org/). F
* `export MES
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/60#discussion_r10243444
--- Diff: docs/configuration.md ---
@@ -134,6 +134,22 @@ Apart from these, the following properties are also
available, and may be useful
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36590950
Merged build finished.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36590951
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12979/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36588476
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36588475
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 have
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36586768
Done. Please correct me if there's any mistake in my pool English. :D
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36583145
Ah, got it. In that case please expand the doc for the
spark.mesos.checkpoint entry to explain that, and maybe link to the
corresponding Mesos docs. Otherwise the current de
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36484334
Merged build finished.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36484336
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12961/
---
If your project i
Github user iven commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36484214
If checkpoint is enabled both in spark and Mesos slaves, the slaves will
write spark and executors information periodically to the disk. Yes, it's used
for Spark to survive sl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36482490
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36482491
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 th
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36481768
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
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36481666
CC @benh
---
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 a
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36481635
What does "checkpoint" do exactly, and why not have it on by default? Is it
for Spark to survive slave restarts?
---
If your project is set up for it, you can reply to this
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36481638
Jenkins, this is 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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-36480715
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 proje
GitHub user iven opened a pull request:
https://github.com/apache/spark/pull/60
Add role and checkpoint support for Mesos backend
This commit also changes Mesos version to 0.14.0, which is the earliest
version supporting these features.
You can merge this pull request into a Git
28 matches
Mail list logo
