You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2018/02/06 01:49:00 UTC

[jira] [Commented] (HDFS-11360) HDFS balancer need a config to appoint to a decided nameservice

    [ https://issues.apache.org/jira/browse/HDFS-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353212#comment-16353212 ] 

Bharat Viswanadham commented on HDFS-11360:
-------------------------------------------

Hi [~cltlfcjin]
 final Collection<URI> namenodes = DFSUtil.getNsServiceRpcUris(conf);
If DFS_INTERNAL_NAMESERVICES_KEY is set, the above namenodes only return the uri that belongs to its cluster.

 

As, DFSUtil.getInternalNsRpcUris(), calls getInternalNameServices(), which will return the above value if it is set, otherwise it will use dfs.nameservices and return all the nameservices. So, if dfs.internal.nameservices is set, it will only create one NameNodeConnector.

 

Could you please let me know if i am missing something here.

> HDFS balancer need a config to appoint to a decided nameservice
> ---------------------------------------------------------------
>
>                 Key: HDFS-11360
>                 URL: https://issues.apache.org/jira/browse/HDFS-11360
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer &amp; mover
>    Affects Versions: 2.7.1
>            Reporter: Lantao Jin
>            Priority: Minor
>
> With distcp configuration, there are two or more "nameservices" setting in hdfs-site.xml, for example:
> {code}
>     <property>
>         <name>dfs.nameservices</name>
>         <value>one-nn-ha,two-nn-ha</value>
>     </property>
> {code}
> If the HDFS Balancer also launches in that node, it will create two IPC threads to connect both of NNs. And block removing both happens in this Balancer. Although I didn't find any block removing between different clusters, the behavior still became weird and unexpected.
> So the best way is adding a configuration that appoint to a decided nameservice to launch. I can offer a patch. Any better ideal? 



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

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