[
https://issues.apache.org/jira/browse/MAPREDUCE-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192409#comment-13192409
]
Hitesh Shah commented on MAPREDUCE-3703:
----------------------------------------
@Eric, 1 MB worth of data being pulled may be an issue depending on where the
call is being made from. If most of the use cases are from more or less within
the same network/colo, then latency may not be that big a factor ( unless
someone hits the jmx url too often ). In any case, if no one has mentioned
anything with respect to the jmx data size for the 0.20 branch, I guess there
is no harm in adding it also to .23.
Minor comments on the json keys:
- could you change UsedMemory and AvailableMemory to UsedMemoryMB and
AvailableMemoryMB.
- Also, it would be good if the json output could be changed to have the keys
match the elements used in the webservice apis.
> 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
