Non-terminal states are gauges (instantaneous measurements) whereas the
terminal states are counters (always increasing, at least for the lifetime
of a master process).
Hopefully this image doesn't get stripped, but we improved the wording here
to clarify which are gauges and which are counters:
>My point is there is no straightforward way of telling how many tasks had
been running on the cluster since it is up. Or am i missing something?
I think we could get it from sum up "master/task_*" metrics?
On Wed, Feb 24, 2016 at 9:04 PM, Geoffroy Jabouley <
geoffroy.jabou...@gmail.com> wrote:
Thanks for the clarification. Does staged means "currently in staging state"?
In previous versions of Mesos (at least 0.22.1), the Staged value was
increased for each staged tasks, to you could tell "X tasks have been
executed on the cluster".
My point is there is no straightforward way of tellin
If you have some tasks which state is not equal to TASK_STAGING, it would
become non-zero.
On Wed, Feb 24, 2016 at 8:23 PM, Geoffroy Jabouley <
geoffroy.jabou...@gmail.com> wrote:
> Hi again
>
> just checked the /metrics/snapshot endpoint. Staged value is zero. Is this
> normal?
>
> {
>"alloc
Hi again
just checked the /metrics/snapshot endpoint. Staged value is zero. Is this
normal?
{
"allocator\/event_queue_dispatches":0.0,
"frameworks\/jenkins\/messages_processed":9.0,
"frameworks\/jenkins\/messages_received":9.0,
"master\/cpus_percent":0.0958,
"master\/cp
Hi, I am not sure whether your problem related to this issue
https://issues.apache.org/jira/browse/MESOS-3282 or not. And could you also
help check "master/tasks_staging" value in your "master/metrics/snapshot"
endpoint? I think "Staged" value is got from that.
On Wed, Feb 24, 2016 at 1:23 AM, Geo
6 matches
Mail list logo
