[HDFS-11956] Do not require a storage ID or target storage IDs when writing a block - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Blocker
Resolution: Fixed
Affects Version/s: 3.0.0-alpha4
Fix Version/s: 3.0.0-alpha4
Component/s: None
Labels:
None

Target Version/s:

3.0.0-alpha4
Release Note:

Hide
Hadoop 2.x clients do not pass the storage ID or target storage IDs when writing a block. For backwards compatibility, the DataNode will not require the presence of these fields. This means older clients are unable to write to a particular storage as chosen by the NameNode (e.g. ~~HDFS-9806~~).

Show
Hadoop 2.x clients do not pass the storage ID or target storage IDs when writing a block. For backwards compatibility, the DataNode will not require the presence of these fields. This means older clients are unable to write to a particular storage as chosen by the NameNode (e.g. HDFS-9806 ).

Description

Seems like ~~HDFS-9807~~ broke backwards compatibility with Hadoop 2.x clients. When talking to a 3.0.0-alpha4 DN with security on:

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 []

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HDFS-11956.004.patch
26/Jun/17 09:42
4 kB
Ewan Higgs
HDFS-11956.003.patch
15/Jun/17 22:55
17 kB
Ewan Higgs
HDFS-11956.002.patch
14/Jun/17 23:15
16 kB
Ewan Higgs
HDFS-11956.001.patch
14/Jun/17 17:36
14 kB
Ewan Higgs

Issue Links

is broken by

HDFS-9807 Add an optional StorageID to writes

Resolved

Activity

People

Assignee:: Ewan Higgs

Reporter:: Andrew Wang

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: 09/Jun/17 06:06

Updated:: 26/Jun/17 18:50

Resolved:: 26/Jun/17 18:20