You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Konstantin Shvachko (Jira)" <ji...@apache.org> on 2022/02/22 19:57:00 UTC
[jira] [Updated] (HADOOP-8299) ViewFileSystem link slash mount point crashes with IndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/HADOOP-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-8299:
----------------------------------------
Fix Version/s: 2.10.1
> ViewFileSystem link slash mount point crashes with IndexOutOfBoundsException
> ----------------------------------------------------------------------------
>
> Key: HADOOP-8299
> URL: https://issues.apache.org/jira/browse/HADOOP-8299
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
> Affects Versions: 3.0.0-alpha1
> Reporter: Eli Collins
> Assignee: Manoj Govindassamy
> Priority: Major
> Fix For: 3.0.0-alpha2, 2.10.1
>
> Attachments: HADOOP-8299.01.patch, HADOOP-8299.02.patch
>
>
> We currently assume [a typical viewfs client configuration|https://issues.apache.org/jira/secure/attachment/12507504/viewfs_TypicalMountTable.png] is a set of non-overlapping mounts. This means every time you want to add a new top-level directory you need to update the client-side mountable config. If users could specify a slash mount, and then add additional mounts as necessary they could add a new top-level directory without updating all client configs (as long as the new top-level directory was being created on the NN the slash mount points to). This could be achieved by HADOOP-8298 (merge mounts, since we're effectively merging all new mount points with slash) or having the notion of a "default NN" for a mount table.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org