hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10356) Ozone: Container server needs enhancements to control of bind address for greater flexibility and testability.
Date Mon, 02 May 2016 17:49:13 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-10356:
---------------------------------
    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.  (was: 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 control the exact network interface selected.  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.)

> Ozone: Container server needs enhancements to control of bind address for greater flexibility
and testability.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10356
>                 URL: https://issues.apache.org/jira/browse/HDFS-10356
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Chris Nauroth
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message