Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 16 Jun 2017 16:53:00 +0000 (UTC)
From: "Wei-Chiu Chuang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13078514.1496988408000.35102.1497631980093@Atlassian.JIRA>
In-Reply-To: <JIRA.13078514.1496988408000@Atlassian.JIRA>
References: <JIRA.13078514.1496988408000@Atlassian.JIRA> <JIRA.13078514.1496988408246@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-11956) Fix BlockToken compatibility with
 Hadoop 2.x clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 16 Jun 2017 16:53:04 -0000


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

Wei-Chiu Chuang commented on HDFS-11956:
----------------------------------------

Hey Ewans, could you please elaborate a little bit more on this config key?
For example, instead of "will allow older clients to access the system" maybe you can be more precise and say this will allow old clients (Hadoop 2.x) to access a Hadoop 3 cluster?
Also, "but will prevent some newer features from working." might be better to mention you mean features added in Hadoop 3. But the way, what are the new features that would not work? Looking at HDFS-9807, looks like disabling it would break HSM block placement policy.

> Fix BlockToken compatibility with Hadoop 2.x clients
> ----------------------------------------------------
>
>                 Key: HDFS-11956
>                 URL: https://issues.apache.org/jira/browse/HDFS-11956
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0-alpha4
>            Reporter: Andrew Wang
>            Assignee: Ewan Higgs
>            Priority: Blocker
>         Attachments: HDFS-11956.001.patch, HDFS-11956.002.patch, HDFS-11956.003.patch
>
>
> Seems like HDFS-9807 broke backwards compatibility with Hadoop 2.x clients. When talking to a 3.0.0-alpha4 DN with security on:
> {noformat}
> 2017-06-06 23:27:22,568 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Block token verification failed: op=WRITE_BLOCK, remoteAddress=/172.28.208.200:53900, message=Block token with StorageIDs [DS-c0f24154-a39b-4941-93cd-5b8323067ba2] not valid for access with StorageIDs []
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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