[
https://issues.apache.org/jira/browse/HDFS-13857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Íñigo Goiri updated HDFS-13857:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.1.2
3.0.4
2.9.2
3.2.0
2.10.0
Status: Resolved (was: Patch Available)
> 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
> Fix For: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
