Re: Tasks may be explicitly dropped by agent in Mesos 1.5

This is a new behavior we have after solving MESOS-1720, and thus a new problem only in 1.5.x. Prior to 1.5, reordered tasks (to the same executor) will be launched because whoever comes first will launch the executor. Since 1.5, one might be dropped. On Mar 1, 2018 4:36 PM, "Gilbert Song"

Re: Tasks may be explicitly dropped by agent in Mesos 1.5

CORRECTION: This is a new behavior that only appears in the current 1.5.x branch. In 1.5.0, Mesos agent still has the old behavior, namely, any reordered tasks (to the same executor) are launched regardless. On Fri, Mar 2, 2018 at 9:41 AM, Chun-Hung Hsiao wrote: >

Re: Tasks may be explicitly dropped by agent in Mesos 1.5

Gilbert I think you're right. The code path doesn't exist in 1.5.0. On Mar 2, 2018 9:36 AM, "Chun-Hung Hsiao" wrote: > This is a new behavior we have after solving MESOS-1720, and thus a new > problem only in 1.5.x. Prior to 1.5, reordered tasks (to the same executor) >

Re: Thoughts on initial implementation to use libarchive?

Jeff, I looked a brief look, this looks great! 1. Is the API reasonable, more or less? Yeah, it looks reasonable to me. 2. Is the name of the API reasonable? Andy suggested namespace archive, > so you could do something like "archive::extract", but unfortunately > libarchive uses that with

Reconsidering `allocatable` check in the allocator

Hi, The allocatable check in the allocator (shown below) was originally introduced to help alleviate the situation where a framework receives some resources, but no cpu/memory, thus cannot launch

Re: Reconsidering `allocatable` check in the allocator

I think (2) would need to be: bool HierarchicalAllocatorProcess::allocatable( const Resources& resources) { if (something outside {cpu, mem, disk} is present) return true else return true iff at least one of {cpu, mem, disk} has >= {MIN_CPU, MIN_MEM, MIN_DISK} } Otherwise, 1 GPU would be

Looking for a shepherd for MESOS-4965

Hi, As our workload using persistent volume increases, the support for resizing volumes gets more important to us, especially for our space efficiency. Can someone familiar with the topic help to shepherd? I can work on design and

Re: Thoughts on initial implementation to use libarchive?

Having both decompress.hpp and gzip.hpp seems unfortunate, can you look into unifying them? The latter is an existing library that provides the following: -In-memory gzip compression and de-compression

Submit a talk to Mesosphere Advance - due March 16th

*Hi Everyone, Mesosphere is proud to announce that the CFP is open for Mesosphere Advance, a new conference focused on DC/OS and Apache Mesos best practices, user stories, and internals. The European conference will be on May 1st, 2018 in

[GitHub] mesos pull request #268: Don't mention the deceased mesos-health-check binar...

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