hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Íñigo Goiri (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HDFS-13857) RBF: Choose to enable the default nameservice to read/write files
Date Tue, 04 Sep 2018 16:21:00 GMT

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

Íñigo Goiri commented on HDFS-13857:

+1 on  [^HDFS-13857.005.patch].
I made the JIRA title a little more general.

> RBF: Choose to enable the default nameservice to read/write files
> -----------------------------------------------------------------
>                 Key: HDFS-13857
>                 URL: https://issues.apache.org/jira/browse/HDFS-13857
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: federation, hdfs
>    Affects Versions: 3.0.0, 3.1.0, 2.9.1
>            Reporter: yanghuafeng
>            Assignee: yanghuafeng
>            Priority: Major
>         Attachments: HDFS-13857.001.patch, HDFS-13857.002.patch, HDFS-13857.003.patch,
HDFS-13857.004.patch, HDFS-13857.005.patch
> The default nameservice can provide some default properties for the namenode protocol.
And if we cannot find the path, we will get a location in default nameservice. From my side
as cluster administrator, we need all files to be written in the location from the MountTableEntry.
If no responding location, some error will return. It is not better to happen some files are
written in some unknown location. We should provide a specific parameter to enable the default
nameservice to store files.

This message was sent by Atlassian JIRA

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

View raw message