Re: Normalization of metric keys

I don't think the lack of principal normalization was intentional. Why spread that further? Don't we also have some normalization today? Having slashes show up in components complicates parsing (can no longer split on '/'), no? For example, if we were to introduce the ability to query a subset of

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

Fixes have been committed and back ported to 1.6.x branch. Please feel free to cut next RC at your convenience. Thanks! On Tue, Jul 3, 2018 at 3:37 PM Greg Mann wrote: > Hey folks, an update on the 1.6.1-rc2 candidate: an issue surfaced after > the fix was merged for MESOS-8830, which is being

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

Hey folks, an update on the 1.6.1-rc2 candidate: an issue surfaced after the fix was merged for MESOS-8830, which is being addressed currently. I'll be AFK for the next 3 days, so I'll cut 1.6.1-rc2 this coming Monday. Sorry for the delay! Cheers, Greg On Mon, Jul 2, 2018 at 12:30 PM, Greg Mann

Normalization of metric keys

Hi all! I'm currently working on adding a suite of new per-framework metrics to help schedulers better debug unexpected/unwanted behavior (MESOS-8842 ). One issue that has come up during this work is how we should handle strings like the framework

implicit mesos-local support in scheduler drivers

Hi all, I found recently, that the Mesos scheduler drivers will implicitly spin up a `mesos-local` cluster for testing if your scheduler uses the Mesos scheduler drivers, specifies “local” as the master, and exports “MESOS_" environment variables to configure the master. Do any scheduler