You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2015/08/03 23:33:05 UTC
[jira] [Updated] (MESOS-1841) Mesos components should expose their
version on an endpoint.
[ https://issues.apache.org/jira/browse/MESOS-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler updated MESOS-1841:
-----------------------------------
Shepherd: Benjamin Mahler
> Mesos components should expose their version on an endpoint.
> ------------------------------------------------------------
>
> Key: MESOS-1841
> URL: https://issues.apache.org/jira/browse/MESOS-1841
> Project: Mesos
> Issue Type: Improvement
> Reporter: David Robinson
> Assignee: haosdent
> Priority: Minor
> Labels: twitter
>
> The libraries (used by scheduler and executor) should expose their version on an endpoint.
> {noformat:title=stats exposed by the scheduler driver}
> # netstat -dnatp | grep LISTEN | grep java
> tcp 0 0 0.0.0.0:48747 0.0.0.0:* LISTEN 1699/java
> tcp 0 0 :::8081 :::* LISTEN 1699/java
> # curl -s http://localhost:48747/metrics/snapshot | python2.7 -m json.tool
> {
> "scheduler/event_queue_messages": 0,
> "system/cpus_total": 24,
> "system/load_15min": 0.18,
> "system/load_1min": 0.29,
> "system/load_5min": 0.2,
> "system/mem_free_bytes": 7850483712,
> "system/mem_total_bytes": 33534873600
> }
> {noformat}
> Likewise, for the master and slave, a lightweight endpoint is desired, see MESOS-2644 as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)