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

Phil Zampino updated KNOX-1167:
-------------------------------
    Description: 
In HDP 3, there will be support for multiple NameNode clusters (HDFS 
Federation), qualified by disitinct namespaces, in a single Hadoop cluster.

Knox needs to provide the ability to distinguish these NN clusters in its 
topologies for proxying WEBHDFS; the most practical means is a service 
parameter.

The behavior for following needs to be defined:
 * Multiple NN clusters, and a descriptor which does not specify such a 
namespace. Which NN cluster will be chosen at discovery-time?

  was:
In HDP 3, there will be support for multiple NameNode clusters, qualified by 
disitinct namespaces, in a single Hadoop cluster.

Knox needs to provide the ability to distinguish these NN clusters in its 
topologies for proxying WEBHDFS; the most practical means is a service 
parameter.

The behavior for following needs to be defined:
 * Multiple NN clusters, and a descriptor which does not specify such a 
namespace. Which NN cluster will be chosen at discovery-time?


> Support Multiple NameNode clusters in Knox topologies
> -----------------------------------------------------
>
>                 Key: KNOX-1167
>                 URL: https://issues.apache.org/jira/browse/KNOX-1167
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.14.0, 1.0.0
>            Reporter: Phil Zampino
>            Assignee: Phil Zampino
>            Priority: Major
>             Fix For: 1.1.0
>
>
> In HDP 3, there will be support for multiple NameNode clusters (HDFS 
> Federation), qualified by disitinct namespaces, in a single Hadoop cluster.
> Knox needs to provide the ability to distinguish these NN clusters in its 
> topologies for proxying WEBHDFS; the most practical means is a service 
> parameter.
> The behavior for following needs to be defined:
>  * Multiple NN clusters, and a descriptor which does not specify such a 
> namespace. Which NN cluster will be chosen at discovery-time?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to