Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 12 Apr 2012 20:59:20 +0000 (UTC)
From: "Daryn Sharp (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <281278635.19160.1334264360256.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1239392150.19048.1334263399172.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-3268) Hdfs mishandles token service &
 incompatible with HA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daryn Sharp updated HDFS-3268:
------------------------------

    Attachment: HDFS-3268.patch

Modified {{Hdfs}} to not overwrite the token service.  Changed {{DistributedFileSystem}} and {{Hdfs}} to call down into {{DFSClient}} to get the token service.  This simplifies the code and eliminates a false coupling between the filesystem and feature of the underlying {{DFSClient}}.
                
> Hdfs mishandles token service & incompatible with HA
> ----------------------------------------------------
>
>                 Key: HDFS-3268
>                 URL: https://issues.apache.org/jira/browse/HDFS-3268
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, hdfs client
>    Affects Versions: 0.24.0, 2.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>         Attachments: HDFS-3268.patch
>
>
> The {{Hdfs AbstractFileSystem}} is overwriting the token service set by the {{DFSClient}}.  The service is not necessarily the correct one since {{DFSClient}} is responsible for the service.  Most importantly, this improper behavior is overwriting the HA logical service which indirectly renders {{FileContext}} incompatible with HA.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira