You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Ken Sipe (JIRA)" <ji...@apache.org> on 2017/03/09 17:31:37 UTC

[jira] [Updated] (MESOS-7224) Provide Access to Master Info

     [ https://issues.apache.org/jira/browse/MESOS-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ken Sipe updated MESOS-7224:
----------------------------
    Description: 
While it is possible to get framework details and agent details from state.json or state-summary.  There isn't an access point for getting master information.   
It would very useful to have an access point that provides that information.

a collection of what is in zk would be fantastic.  

example return:

{code}
{
	hostname: "10.0.6.183",
	cluster: "ken-v6ndoid",
	masters: [
		{"address":{"hostname":"10.0.6.183","ip":"10.0.6.183","port":5050},"hostname":"10.0.6.183","id":"832b06e2-5826-4823-8b6e-6df723865be6","ip":3070623754,"pid":"master@10.0.6.183:5050","port":5050,"version":"1.2.0"},
		{"address":{"hostname":"10.0.4.68","ip":"10.0.4.68","port":5050},"hostname":"10.0.4.68","id":"c5c03ffe-f37f-4503-b2b5-e7cf2c88c6b6","ip":1141112842,"pid":"master@10.0.4.68:5050","port":5050,"version":"1.2.0"},
		{"address":{"hostname":"10.0.5.52","ip":"10.0.5.52","port":5050},"hostname":"10.0.5.52","id":"032c3c33-32f5-4e61-b8d4-21c23275f18e","ip":872742922,"pid":"master@10.0.5.52:5050","port":5050,"version":"1.2.0"}
	],
	leader: "10.0.6.183"
}

{code}

  was:
While it is possible to get framework details and agent details from state.json or state-summary.  There isn't an access point for getting master information.   
It would very useful to have an access point that provides that information.

a collection of what is in zk would be fantastic.  

example return:

```
{
	hostname: "10.0.6.183",
	cluster: "ken-v6ndoid",
	masters: [
		{"address":{"hostname":"10.0.6.183","ip":"10.0.6.183","port":5050},"hostname":"10.0.6.183","id":"832b06e2-5826-4823-8b6e-6df723865be6","ip":3070623754,"pid":"master@10.0.6.183:5050","port":5050,"version":"1.2.0"},
		{"address":{"hostname":"10.0.4.68","ip":"10.0.4.68","port":5050},"hostname":"10.0.4.68","id":"c5c03ffe-f37f-4503-b2b5-e7cf2c88c6b6","ip":1141112842,"pid":"master@10.0.4.68:5050","port":5050,"version":"1.2.0"},
		{"address":{"hostname":"10.0.5.52","ip":"10.0.5.52","port":5050},"hostname":"10.0.5.52","id":"032c3c33-32f5-4e61-b8d4-21c23275f18e","ip":872742922,"pid":"master@10.0.5.52:5050","port":5050,"version":"1.2.0"}
	],
	leader: "10.0.6.183"
}

```


> Provide Access to Master Info
> -----------------------------
>
>                 Key: MESOS-7224
>                 URL: https://issues.apache.org/jira/browse/MESOS-7224
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Ken Sipe
>
> While it is possible to get framework details and agent details from state.json or state-summary.  There isn't an access point for getting master information.   
> It would very useful to have an access point that provides that information.
> a collection of what is in zk would be fantastic.  
> example return:
> {code}
> {
> 	hostname: "10.0.6.183",
> 	cluster: "ken-v6ndoid",
> 	masters: [
> 		{"address":{"hostname":"10.0.6.183","ip":"10.0.6.183","port":5050},"hostname":"10.0.6.183","id":"832b06e2-5826-4823-8b6e-6df723865be6","ip":3070623754,"pid":"master@10.0.6.183:5050","port":5050,"version":"1.2.0"},
> 		{"address":{"hostname":"10.0.4.68","ip":"10.0.4.68","port":5050},"hostname":"10.0.4.68","id":"c5c03ffe-f37f-4503-b2b5-e7cf2c88c6b6","ip":1141112842,"pid":"master@10.0.4.68:5050","port":5050,"version":"1.2.0"},
> 		{"address":{"hostname":"10.0.5.52","ip":"10.0.5.52","port":5050},"hostname":"10.0.5.52","id":"032c3c33-32f5-4e61-b8d4-21c23275f18e","ip":872742922,"pid":"master@10.0.5.52:5050","port":5050,"version":"1.2.0"}
> 	],
> 	leader: "10.0.6.183"
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)