Hi,
We have framework that launched Spark jobs on our Mesos cluster. We are
currently having an issue where Spark jobs are getting stuck due to some
timeout issue. We have cancel functionality that would kill send task_kill
message to master. When the jobs get stuck Spark driver task is not
Github user carlonelong commented on the issue:
https://github.com/apache/mesos/pull/280
Sorry, my bad. Check again pls. @xujyan
---
Thanks for the update!
On Sat, Mar 31, 2018 at 7:44 AM Gilbert Song wrote:
> Thanks for the awesome update, Greg!
>
> - Gilbert
>
> On Fri, Mar 30, 2018 at 6:20 PM, Vinod Kone wrote:
>
> > Thanks for the update Greg!
> >
> > Sent from my phone
> >
> > >
Github user m9a commented on the issue:
https://github.com/apache/mesos/pull/279
@Gilbert88, @xujyan Sure, I will check about the rbt issue on slack.
---
Github user m9a commented on the issue:
https://github.com/apache/mesos/pull/279
The JIRA for this PR: https://issues.apache.org/jira/browse/MESOS-8750
Since @xujyan is shepherding it I intended to set him as the reviewer but
it doesn't look like I can change those fields on the
Github user xujyan commented on the issue:
https://github.com/apache/mesos/pull/280
Thanks for @carlonelong for the PR. The PR includes some extraneous commits
(see above), could you clean it up?
---
Hi all,
The API working group will be meeting today at 11am PST. We'll be
discussing HTTP return codes in Mesos [1]. If you have any other items for
discussion, add them to the agenda! [2]
Cheers,
Greg
[1] https://issues.apache.org/jira/browse/MESOS-7697
[2]
Hi,
> 1) What would be the criteria for removing `FLAKY` label from a test? Who
will take care of removing this label?
The process would be exactly the same as for removing the `DISABLED` label
today, i.e. whoever feels confident that they fixed the test can remove the
label.
> 2) Do we expect
GitHub user carlonelong opened a pull request:
https://github.com/apache/mesos/pull/280
Fix wrong example of executor message.
The example of executor message in executor-http-api.md is wrong. This
patch fixes this.
You can merge this pull request into a Git repository by