Re: [Proposal] Updating levels for verbose logging

To elaborate on this, ideally libprocess logging is configurable by the user in a flexible manner that gives them control. For example, in LevelDB you can pass in the info 'Logger' that it will use for logging: https://github.com/google/leveldb/blob/v1.20/include/leveldb/options.h#L64-L68 I'm

Re: [Proposal] Updating levels for verbose logging

Ben, I understand why you question that libprocess should log starting from a specific level. I think it is not quite illogical for a library to use lower priority levels. I can see this change being helpful for any user of libprocess, not just Mesos. On Mon, Oct 9, 2017 at 6:34 PM, Benjamin

Re: [Proposal] Fetcher extract path

+1. Could you file a JIRA laying out the problem and the proposal? Here a link about submitting a patch: http://mesos.apache.org/documentation/latest/ submitting-a-patch/ Note that there's already an output_file

Re: Updating running tasks in-place

--- Jiang Yan Xu | @xujyan On Wed, Oct 4, 2017 at 11:50 AM, Zhitao Li wrote: > Thanks for taking the lead, Yan! Replying to your points inline: > > On Wed, Oct 4, 2017 at 11:11 AM, Yan Xu wrote: > > > Hi Mesos

[GitHub] mesos pull request #237: Documentation: Fix event syntax by wrapping a task ...

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

Re: Adding the limited resource to TaskStatus messages

> On Oct 9, 2017, at 1:27 PM, Vinod Kone wrote: > >> In the case that a task is killed because it violated a resource >> constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, >> REASON_CONTAINER_LIMITATION_DISK or REASON_CONTAINER_LIMITATION_MEMORY), >> this

Re: Adding the limited resource to TaskStatus messages

> In the case that a task is killed because it violated a resource > constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, > REASON_CONTAINER_LIMITATION_DISK or REASON_CONTAINER_LIMITATION_MEMORY), > this field may be populated with the resource that triggered the > limitation. This is

Re: organizing a "docathon"

Please see this doc for more details as well as ideas for documentation. Please add more yourself! On Wed, Oct 4, 2017 at 6:19 PM Benjamin Hindman wrote: > We've decided on

Re: Adding the limited resource to TaskStatus messages

Does it make sense to wrap the resources in a `Limitation` message in case we add new fields for it? --- Jiang Yan Xu | @xujyan On Mon, Oct 9, 2017 at 10:56 AM, James Peach wrote: > Hi all, > > In https://reviews.apache.org/r/62644/,

Re: [Proposal] Updating levels for verbose logging

Thanks for your input Benjamin. After having looked at per-module verbose level, here are the changes I would like to apply: 1. Changing the Mesos common events verbose logs so that they use VLOG(2) instead of 1. The original commit https://github.com/apache/meso

Adding the limited resource to TaskStatus messages

Hi all, In https://reviews.apache.org/r/62644/, I am proposing to add an optional Resources field to the TaskStatus message named `limited_resources`. In the case that a task is killed because it violated a resource constraint (ie. the reason field is REASON_CONTAINER_LIMITATION,

[Proposal] Fetcher extract path

Hi all, I'm using the Mesos fetcher to download artifacts (e.g. ZIP archives) to the sandbox prior to running a task. I noticed that the archive content is always extracted to the sandbox root directory (when extract=true) and there is currently no way to provide a different path where the