You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2013/02/19 19:31:12 UTC
[jira] [Updated] (AMBARI-1443) Should use defaults when missing JMX
port info from configuration
[ https://issues.apache.org/jira/browse/AMBARI-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Beerbower updated AMBARI-1443:
----------------------------------
Attachment: AMBARI-1443.patch
> Should use defaults when missing JMX port info from configuration
> ------------------------------------------------------------------
>
> Key: AMBARI-1443
> URL: https://issues.apache.org/jira/browse/AMBARI-1443
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 1.2.2
>
> Attachments: AMBARI-1443.patch
>
>
> There was a recent change to get JMX port information from configuration rather than use hard coded values. It looks like it is possible that the port information may be missing or incomplete. I see the following ...
> {code}
> {JOBTRACKER=50030, HBASE_MASTER=null, NAMENODE=50070, TASKTRACKER=null, DATANODE=50075}
> {code}
> Note the missing port values for HBASE_MASTER and TASKTRACKER. In this case we will not show any JMX metrics for those components.
> We should use the default values when the JMX port values are not available from configuration.
> |NAMENODE|50070
> |DATANODE|50075
> |JOBTRACKER|50030
> |TASKTRACKER|50060
> |HBASE_MASTER|60010
--
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