Re: 1.4.1 release

We want to backport https://reviews.apache.org/r/62518/ to 1.2.x, 1.3.x and 1.4.x, James will work on it. Regards, Qian Zhang On Fri, Nov 3, 2017 at 12:11 AM, Kapil Arya wrote: > Please reply to this email if you have pending patches to be backported to > 1.4.x as we are

Re: TASK_UNKNOWN status ambiguousness

+1 On Thu, Nov 2, 2017 at 1:15 PM, Ilya Pronin wrote: > Hey everyone, > > Currently, TASK_UNKNOWN task status covers 2 different cases that should be > handled differently by frameworks: > 1. Task is unknown, agent is unknown: the fate of the task is unknown, the >

Re: 1.3.2 Release

Great! I cherry picked Gaston's fix for https://issues.apache.org/ jira/browse/MESOS-8135. On Wed, Nov 1, 2017 at 6:57 PM, Michael Park wrote: > Please reply to this email if you have pending patches to be backported to > 1.3.x, I'm aiming to cut a 1.3.2 on Friday. > >

Re: clearing the executor authentication token from the task environment

> On Nov 1, 2017, at 2:28 PM, James Peach wrote: > > Hi all, > > In https://issues.apache.org/jira/browse/MESOS-8140, I'm proposing that we > clear the MESOS_EXECUTOR_AUTHENTICATION_TOKEN environment variable > immediately after consuming it in the built-in executors. This

TASK_UNKNOWN status ambiguousness

Hey everyone, Currently, TASK_UNKNOWN task status covers 2 different cases that should be handled differently by frameworks: 1. Task is unknown, agent is unknown: the fate of the task is unknown, the framework may elect to wait until its agent comes back (network partition resolves, etc.); 2.

[GitHub] mesos pull request #247: Fixed reference to Mesos paper in the documentation...

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/247#discussion_r148613763 --- Diff: docs/architecture.md --- @@ -34,4 +34,4 @@ In addition, this resource offer process repeats when tasks finish and new resou While the

[GitHub] mesos pull request #247: Fixed reference to Mesos paper in the documentation...

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/247#discussion_r148613391 --- Diff: docs/architecture.md --- @@ -34,4 +34,4 @@ In addition, this resource offer process repeats when tasks finish and new resou While the

[GitHub] mesos issue #247: Fixed reference to Mesos paper in the documentation.

Github user andschwa commented on the issue: https://github.com/apache/mesos/pull/247 You can use Autotools too, I just don't know what the target is, and don't like to wait around for the entire build 😛 ---

[GitHub] mesos issue #247: Fixed reference to Mesos paper in the documentation.

Github user mpereira commented on the issue: https://github.com/apache/mesos/pull/247 @andschwa thanks for clarifying. I'll try that again soon, it looks like I'm missing a few dependencies for this cmake build. ---

[GitHub] mesos issue #247: Fixed reference to Mesos paper in the documentation.

Github user andschwa commented on the issue: https://github.com/apache/mesos/pull/247 @mpereira Oh I know what's going on: > Please make sure Java proto files are generated in ../build/src/java/generated folder. The site generator expects the build to have been run,

[GitHub] mesos pull request #247: Fixed reference to Mesos paper in the documentation...

GitHub user mpereira opened a pull request: https://github.com/apache/mesos/pull/247 Fixed reference to Mesos paper in the documentation. The paper is also available at https://people.eecs.berkeley.edu/~alig/papers/mesos.pdf but I noticed it was already included in the site's

1.4.1 release

Please reply to this email if you have pending patches to be backported to 1.4.x as we are aiming to cut a release candidate for 1.4.1 early next week. Thanks, Anand and Kapil

[GitHub] mesos pull request #246: sched-http-api: fix example JSON

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/246 ---

[GitHub] mesos pull request #246: sched-http-api: fix example JSON

GitHub user jdef opened a pull request: https://github.com/apache/mesos/pull/246 sched-http-api: fix example JSON You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdef/mesos patch-1 Alternatively you can review and apply these