[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user jieyu commented on the issue: https://github.com/apache/mesos/pull/303 @fcuny We prefer reviewboard for non trivial changes. ---

[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user fcuny commented on the issue: https://github.com/apache/mesos/pull/303 That sounds reasonable. I'll get to update the review with this. Should I move the review to reviewboard or keep iterating here ? ---

[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user jieyu commented on the issue: https://github.com/apache/mesos/pull/303 Looks like on CentOS 7 (3.10.0-693.5.2.el7.x86_64). If kmem accounting is not enabled, the `memory.kmem.limit_in_bytes` will always show 0. And reading `memory.kmem.slabinfo` will give `Input/output

Re: Operations Working Group - First Meeting

Please count me on. Looking forward to it. Sent from my iPhone > On Jul 20, 2018, at 4:05 PM, Gastón Kleiman wrote: > > Hi Abel, > > I would love to learn more from people operating Mesos clusters of any > size. We can discuss what is working great, what is on the roadmap, and > what could be

[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user jieyu commented on the issue: https://github.com/apache/mesos/pull/303 I am not sure if the kernel behavior has changed or not in newer kernels. For example:

[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user fcuny commented on the issue: https://github.com/apache/mesos/pull/303 We've been running with this patch at Twitter since February and we're getting kmem metrics. The mentioned bug is interesting, we've only been running with 4.9 and later. ---

Re: Operations Working Group - First Meeting

Hi Abel, I would love to learn more from people operating Mesos clusters of any size. We can discuss what is working great, what is on the roadmap, and what could be improved. Some of us have been working on adding new per-framework metrics and extra logging to the Mesos master - I think that an

[GitHub] mesos issue #303: Expose new metrics for memory usage in the container.

Github user jieyu commented on the issue: https://github.com/apache/mesos/pull/303 I don't think we turn on kmem accounting yet in Mesos containerizer. I remember in old kernels, you need to set kmem.limit_in_bytes once to enable kmem accounting. I am not sure about the new

[GitHub] mesos pull request #303: Expose new metrics for memory usage in the containe...

GitHub user fcuny opened a pull request: https://github.com/apache/mesos/pull/303 Expose new metrics for memory usage in the container. The metric "mem_kmem_usage_bytes" is the total kernel memory usage by processes in the cgroup in bytes. The metric

[GitHub] mesos pull request #301: Document SUPPRESS HTTP call [MESOS-7211]

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/301#discussion_r204166164 --- Diff: docs/scheduler-http-api.md --- @@ -479,6 +479,32 @@ HTTP/1.1 202 Accepted ``` +### SUPPRESS +Sent by the scheduler when

[GitHub] mesos pull request #301: Document SUPPRESS HTTP call [MESOS-7211]

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/301#discussion_r204167169 --- Diff: docs/scheduler-http-api.md --- @@ -479,6 +479,32 @@ HTTP/1.1 202 Accepted ``` +### SUPPRESS +Sent by the scheduler when

Re: [VOTE] Release Apache Mesos 1.3.3 (rc1)

MPark— what's the decision regarding the 1.3.3 release? On Mon, Jul 9, 2018 at 8:52 PM, Michael Park wrote: > I'm considering simply abandoning the 1.3.3 release and bringing the 1.3.x > branch to end of life. > If anyone really wants a 1.3.3, I'm certainly willing to finish the > release

[RESULT] [VOTE] Move the project repos to gitbox

Hi, This vote has passed with 7 +1s and no 0s or -1s! +1 (binding) - Vinod Kone James Peach Zhitao Li Andrew Schwartzmeyer Jie Yu Greg Mann Gaston Kleiman I'll file an INFRA ticket to get the process in motion. Thanks, Vinod On Tue, Jul 17, 2018 at 8:27 PM Gastón Kleiman wrote: