[HDFS-10356] Ozone: Container server needs enhancements to control of bind address for greater flexibility and testability.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: ozone
• Labels: OzonePostMerge tocheck
• Target Version/s: HDFS-7240
• Assignee: Anu Engineer
• Reporter: Chris Nauroth
• Created: 02/May/16 17:45
• Updated: 14/May/18 17:19
• Resolved: 14/May/18 17:19

Description

The container server, as implemented in class org.apache.hadoop.ozone.container.common.transport.server.XceiverServer, currently does not offer the same degree of flexibility as our other RPC servers for controlling the network interface and port used in the bind call. There is no "bind-host" property, so it is not possible to select all available network interfaces via the 0.0.0.0 wildcard address. If the requested port is different from the actual bound port (i.e. setting port to 0 in test cases), then there is no exposure of that actual bound port to clients.

Issue Links

• Dependent: HDFS-10363 Ozone: Introduce new config keys for SCM service endpoints