You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/02/02 03:52:12 UTC
[jira] [Commented] (AMBARI-1260) Remove hard coded JMX port
mappings
[ https://issues.apache.org/jira/browse/AMBARI-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569402#comment-13569402 ]
Siddharth Wagle commented on AMBARI-1260:
-----------------------------------------
Please review. No hard-coded JMX mappings in this patch, if recommended we can still initialize it to default values
> Remove hard coded JMX port mappings
> -----------------------------------
>
> Key: AMBARI-1260
> URL: https://issues.apache.org/jira/browse/AMBARI-1260
> Project: Ambari
> Issue Type: Improvement
> Components: controller
> Affects Versions: 1.2.1
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.3.0
>
> Attachments: AMBARI-1260.patch
>
>
> The JMXPropertyProvider contains a map of component names to ports ...
> {code}
> JMX_PORTS.put("NAMENODE", "50070");
> JMX_PORTS.put("DATANODE", "50075");
> JMX_PORTS.put("JOBTRACKER", "50030");
> JMX_PORTS.put("TASKTRACKER", "50060");
> JMX_PORTS.put("HBASE_MASTER", "60010");
> {code}
> These ports can change in configuration. Need to create the mapping dynamically.
> This is required for secure HDP cluster to work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira