[
https://issues.apache.org/jira/browse/HDFS-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347375#comment-16347375
]
Bharat Viswanadham commented on HDFS-13062:
-------------------------------------------
Hi [~hanishakoneru]
Thanks for review.
Addressed review comments in patch v05.
*
{quote}In {{setConf()}}, why are we getting the nameserviceIds from the config
key {{DFS_INTERNAL_NAMESERVICES_KEY}} before {{DFS_NAMESERVICES}}? IIUC from
HDFS-6376, which introduced the internal nameservices key, it is meant for
datanodes to distinguish between which nameservices to connect to. JournalNodes
should not be using this configuration to deduce the nameservice Ids. Please
correct me if I am wrong.{quote}If DFS_INTERNAL_NAMESERVICES_KEY is set, those
nameservices belongs to the cluster running, DFS_NAMESERVICES can be set with
nameservices belonging to cluster and external cluster nameservices which it
will be connecting to. So, that is the reason for checking
DFS_INTERNAL_NAMESERVICES_KEY.
> Provide support for JN to use separate journal disk per namespace
> -----------------------------------------------------------------
>
> Key: HDFS-13062
> URL: https://issues.apache.org/jira/browse/HDFS-13062
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Attachments: HDFS-13062.00.patch, HDFS-13062.01.patch,
> HDFS-13062.02.patch, HDFS-13062.03.patch, HDFS-13062.04.patch,
> HDFS-13062.05.patch
>
>
> In Federated HA setup, provide support for separate journal disk for each
> namespace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
