[
https://issues.apache.org/jira/browse/MAPREDUCE-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192291#comment-13192291
]
Eric Payne commented on MAPREDUCE-3703:
---------------------------------------
@Hitesh,
The timing and size did not seem unreasonable during my tests in a 0.20.205
security cluster with a large number of nodes (~4000 nodes).
Size: ~800000 Megabytes
Avg time after 10 accesses to the JMX service (using wget to access the jmx
service):
real: 0m0.1016s
sys: 0m0.0050s
user: 0m0.0014s
Since the load seems reasonable, and since this service is provided in previous
releases, I would like to provide it in 0.23 also.
> ResourceManager should provide node lists in JMX output
> -------------------------------------------------------
>
> Key: MAPREDUCE-3703
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3703
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 0.23.1
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Critical
>
> In 0.20.*, the JMX UI for the JobTracker (http://<JobTrackerHost>:50030/jmx)
> showed lists of Live and BlackListed Nodes under the JobTrackerInfo section.
> In 0.23, the ResourceManager JMX UI shows the number of active,
> decommissioned, lost, unhealthy, and rebooted nodes under the ClusterMetrics
> section, but does not give the list of nodes.
> At least the list of active nodes is needed in JSON format.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
