Re: [Proposal] Updating levels for verbose logging

It seems unfortunate to establish an ordering between different component's verbosity levels, how is libprocess to know which level to start at? I suppose you can tell it, but it's not clear that the first level of verbosity in libprocess should come after the max level of verbosity in mesos.

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

Github user rukletsov commented on a diff in the pull request: https://github.com/apache/mesos/pull/237#discussion_r143264159 --- Diff: docs/executor-http-api.md --- @@ -279,19 +279,21 @@ LAUNCH_GROUP Event (JSON) "launch_group": { "task_group" : {

Re: [Proposal] Updating levels for verbose logging

I support the effort, Armand. On Wed, Oct 4, 2017 at 3:59 PM, Armand Grillet wrote: > Hi all, > > We currently use three levels of verbose logging via the VLOG macro. I > propose to add two levels and change how we use the current ones to make > debugging easier for

[GitHub] mesos pull request #239: Add Nathan Jackson to contributors list.

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

[GitHub] mesos issue #240: Corrected quota to define it as minimal and maximal

Github user rukletsov commented on the issue: https://github.com/apache/mesos/pull/240 Is this comment insufficient? https://github.com/apache/mesos/blame/c87db8c8c8cef3d95e8ddaf7c75353732919edf7/docs/quota.md#L321 Maybe pull it higher then? ---

[GitHub] mesos pull request #240: Corrected quota to define it as minimal and maximal

GitHub user aggress opened a pull request: https://github.com/apache/mesos/pull/240 Corrected quota to define it as minimal and maximal Based on a discussion with @bmahler, the current documented definition of a quota suggests it guarantees only the minimal guarantee, and that a