ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <>
Subject [jira] [Commented] (AMBARI-1260) Remove hard coded JMX port mappings
Date Tue, 05 Feb 2013 16:38:11 GMT


Sumit Mohanty commented on AMBARI-1260:


I was going though the javadoc and this para caught my attention so I asked.
However, eventually correct read is probably sufficient.

ŠNote that this implementation is not synchronized. If multiple threads
access this map concurrently, and at least one of the threads modifies the
map structurally, it must be synchronized externally. (A structural
modification is any operation that adds or deletes one or more mappings;
merely changing the value associated with a key that an instance already
contains is not a structural modification.) This is typically accomplished
by synchronizing on some object that naturally encapsulates the map. If no
such object exists, the map should be "wrapped" using
theCollections.synchronizedMap method. This is best done at creation time,
to prevent accidental unsynchronized access to the map:Š


> Remove hard coded JMX port mappings
> -----------------------------------
>                 Key: AMBARI-1260
>                 URL:
>             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:

View raw message