[HDFS-10625] VolumeScanner to report why a block is found bad - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.7.4
Component/s: datanode, hdfs
Labels:
- supportability

Target Version/s:

2.7.4
Hadoop Flags:

Reviewed

Description

VolumeScanner may report:

WARN org.apache.hadoop.hdfs.server.datanode.VolumeScanner: Reporting bad blk_1170125248_96458336 on /d/dfs/dn

It would be helpful to report the reason why the block is bad, especially when the block is corrupt, where is the first corrupted chunk in the block.

Attachments

Attachments

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

HDFS-10625.patch
14/Jul/16 14:24
0.8 kB
Rushabh Shah
HDFS-10625-1.patch
15/Jul/16 18:57
2 kB
Rushabh Shah
HDFS-10625.003.patch
28/Jul/16 06:42
3 kB
Yiqun Lin
HDFS-10625.004.patch
03/Aug/16 11:46
3 kB
Yiqun Lin
HDFS-10625.005.patch
10/Aug/16 19:44
3 kB
Rushabh Shah

Issue Links

is duplicated by

HDFS-10626 VolumeScanner prints incorrect IOException in reportBadBlocks operation

Resolved

is related to

HDFS-10512 VolumeScanner may terminate due to NPE in DataNode.reportBadBlocks

Resolved

HDFS-10587 Incorrect offset/length calculation in pipeline recovery causes block corruption

Resolved

Activity

People

Assignee:: Rushabh Shah

Reporter:: Yongjun Zhang

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: 14/Jul/16 05:43

Updated:: 02/Oct/19 17:14

Resolved:: 29/Aug/16 21:31