Re: Extend HTTP Endpoint to allow querying for metric types

v1 API is not yet declared stable, so we can make changes before 1.0. On Mon, Jun 27, 2016 at 10:10 PM, Tuan-Anh Hoang-Vu wrote: > Hi Vinod, > > Yes! That will also works! My only concern is will this break backward > compatibility? > Would this be something worth pushing

Re: Extend HTTP Endpoint to allow querying for metric types

Hi Vinod, Yes! That will also works! My only concern is will this break backward compatibility? Would this be something worth pushing upstream? On Mon, Jun 27, 2016 at 6:39 PM, Vinod Kone wrote: > I was thinking more along the lines of : > > ``` > GetMetrics { >

Re: Conceptual question Task Container

>Docker engine to create a Docker container as the task and set the resources of that container more than task's resources? As I known, we could not avoid this so far. On Tue, Jun 28, 2016 at 10:52 AM, Qian Zhang wrote: > @Vinod, what if the executor talks to Docker engine

Two important tickets for improving documentation

Just wanted to highlight two tickets that would be of great help to the community. (1) The first is to publish documentation on the website for each release. We currently publish periodically off of master, and so it's a pain for users because the documentation does not reflect the version they

Re: Conceptual question Task Container

@Vinod, what if the executor talks to Docker engine to create a Docker container as the task and set the resources of that container more than task's resources? Will we guard this? Thanks, Qian Zhang On Tue, Jun 28, 2016 at 8:12 AM, Vinod Kone wrote: > A task doesn't get

Re: Extend HTTP Endpoint to allow querying for metric types

I was thinking more along the lines of : ``` GetMetrics { repeated Metric gauges = 1; repeated Metric counters = 2; } ``` On Mon, Jun 27, 2016 at 6:27 PM, Tuan-Anh Hoang-Vu wrote: > Timer will simply measure the amount of time it takes (in ns) for an > operation. > >

Re: Extend HTTP Endpoint to allow querying for metric types

Timer will simply measure the amount of time it takes (in ns) for an operation. On Mon, Jun 27, 2016 at 6:14 PM, Benjamin Mahler wrote: > What is the timer type? Is it effectively a special case of a histogram? > > On Mon, Jun 27, 2016 at 5:34 PM, Tuan-Anh Hoang-Vu

Re: Extend HTTP Endpoint to allow querying for metric types

What is the timer type? Is it effectively a special case of a histogram? On Mon, Jun 27, 2016 at 5:34 PM, Tuan-Anh Hoang-Vu wrote: > Hi Benjamin, > > We used an in-house metrics system, which is basically a time-series > database. > I don't know in details about the metrics

Re: Extend HTTP Endpoint to allow querying for metric types

Hi Vinod, I checked the corresponding master code [1] and also the v1 api response for GET_METRICS call. Do you suggest adding another field called `type` or something into the result, so instead of { "name": "master/cpus_total", "value": 0.0 } we have { "name":

Re: Extend HTTP Endpoint to allow querying for metric types

Hi Benjamin, We used an in-house metrics system, which is basically a time-series database. I don't know in details about the metrics system, but the collection client required me to specify metric type, probably for optimization purpose. It accepts 3 different types: counter, gauge and timer On

Re: Extend HTTP Endpoint to allow querying for metric types

We can definitely distinguish counters and gauges in the upcoming v1 API. https://github.com/apache/mesos/blob/master/include/mesos/v1/master/master.proto#L265 On Mon, Jun 27, 2016 at 5:09 PM, Benjamin Mahler wrote: > It's worth doing because it has come up before [1]

Re: Conceptual question Task Container

A task doesn't get its own cgroup because task was supposed to represent a unit of work. That unit of work doesn't have to be necessarily done via a unix process or container. For example, the executor might realize a task as a thread! That said, we did talk about providing an API for executors

Re: Extend HTTP Endpoint to allow querying for metric types

It's worth doing because it has come up before [1] [2]. For our own education, in your case why is the metrics collection system interested in the type? Is it for optimization? Which metrics collection system are you using? What are the types that the metrics collection system understands? The

Re: Please add me as contributor

Great. Can you send a PR adding yourself to https://github.com/apache/mesos/blob/master/docs/contributors.yaml ? On Mon, Jun 27, 2016 at 4:36 AM, Philip Winder wrote: > Hi, > Could you add me as a contributor. I would like to add a PR for improved > documentation for

[GitHub] mesos pull request #115: Added xiaods as contributor.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/115 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Please add me as contributor

Hi, Could you add me as a contributor. I would like to add a PR for improved documentation for this issue: https://issues.apache.org/jira/browse/MESOS-5702 Phil

[GitHub] mesos pull request #115: Added xiaods as contributor.

GitHub user xiaods opened a pull request: https://github.com/apache/mesos/pull/115 Added xiaods as contributor. The contributors.yaml has been updated adding myself as contributor You can merge this pull request into a Git repository by running: $ git pull

[GitHub] mesos pull request #114: Added jvanz as contributor.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/114 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #114: Added jvanz as contributor.

Github user haosdent commented on the issue: https://github.com/apache/mesos/pull/114 haha, you could ignore travis, it always failed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #114: Added jvanz as contributor.

Github user jvanz commented on the issue: https://github.com/apache/mesos/pull/114 How is it possible? I've updated the contributors.yaml only. xD --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[GitHub] mesos pull request #113: Added a file to test PR notifications.

GitHub user mesosprbot opened a pull request: https://github.com/apache/mesos/pull/113 Added a file to test PR notifications. You can merge this pull request into a Git repository by running: $ git pull https://github.com/artemharutyunyan/mesos master Alternatively you can

[GitHub] mesos pull request #114: Added jvanz as contributor.

GitHub user jvanz opened a pull request: https://github.com/apache/mesos/pull/114 Added jvanz as contributor. The contributors.yaml has been updated adding myself as contributor You can merge this pull request into a Git repository by running: $ git pull

Re: Extend HTTP Endpoint to allow querying for metric types

Hi Vinod, Yes, my metric collection system need to distinguish between different metrics. Currently we hard coded all metric types into our system, but it's not very scalable and error prone. For example I recently discovered that we misclassified `timestamp` as gauge instead of counter. On Mon,

Re: Extend HTTP Endpoint to allow querying for metric types

Hey Tuan. Can I ask what you are trying to accomplish here? Does your metric collection system need to distinguish between different metrics? On Mon, Jun 27, 2016 at 10:35 AM, Tuan-Anh Hoang-Vu wrote: > Hello, > > I am planning to extend current metrics endpoint

Re: "sleep" in a libprocess Process

Hi Hans, If you delay, and then the lambda that you schedule is a `defer` on to the same process, then this accomplishes what you want. The one caveat is that other functions may be invoked on your actor process in the mean time. — *Joris Van Remoortere* Mesosphere On Tue, Jun 28, 2016 at 1:14

"sleep" in a libprocess Process

Hi, Is there a way to sleep a libprocess-process ? Or at least some construct to stop for a specific amount of time in the middle of a method, which is member of a Process, but giving opportunity to other processes to handle their messages during that sleep. stout::os::sleep simply stops

Re: mesos/kafka issues (reviving old thread)

To close the loop on this one : With Steve Niemitz's help, I resolved the issue, kafka-scheduler was going to wrong master and the slave it was going to returned a /master/status.json which did not have any information about the registered slaves. "slaves":[ ], What did I do? 1.

[RESULT][VOTE] Release Apache Mesos 0.26.2 (rc1)

Hi all, NOTE: This will be the last supported point release for 0.26.x. The vote for Mesos 0.26.2 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Kapil Arya Benjamin Mahler +1 (Non-binding) -- There were no 0 or -1

Extend HTTP Endpoint to allow querying for metric types

Hello, I am planning to extend current metrics endpoint (/metrics/snapshot) to only return a specific type of metrics (either counter, gauge or timer). It would be great if I can get feedback from you if this is worth pursuing, or there is an existing solution, or my implementation plan is sound.

Re: Conceptual question Task Container

The same is true with all frameworks I've used, such as Marathon - each executor manages one task (although it can have multiple "runs"). On Mon, Jun 27, 2016 at 9:49 AM haosdent wrote: > Hi, @Dave If you use mesos-executor or mesos-docker-executor. It only would > launch

Re: Travis build

Travis CI should be disabled and you could ignore its result now. Refer to https://issues.apache.org/jira/browse/MESOS-5655 On Mon, Jun 27, 2016 at 8:57 AM, José Guilherme Vanz < guilherme@gmail.com> wrote: > Hello folks > > As I can see, all build done by travis CI server are failing. I

Conceptual question Task Container

Hi, I'm currently familiarizing myself with the Mesos source code and have a conceptual question about executors, tasks and the containerizer. Basically, each executor gets its own container (and thus its own cgroup subtree ".../mesos/executor0" when using cgroup isolation). This achieves