[HDFS-9023] When NN is not able to identify DN for replication, reason behind it can be logged - ASF JIRA

Voters

Stop watching

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 2.7.1
Fix Version/s: 3.1.0, 2.10.0, 2.9.1, 3.0.1
Component/s: hdfs-client, namenode
Labels:
None

Target Version/s:

2.9.1, 3.0.1
Hadoop Flags:

Reviewed

Description

When NN is not able to identify DN for replication, reason behind it can be logged (at least critical information why DNs not chosen like disk is full). At present it is expected to enable debug log.

For example the reason for below error looks like all 7 DNs are busy for data writes. But at client or NN side no hint is given in the log message.

File /tmp/logs/spark/logs/application_1437051383180_0610/xyz-195_26009.tmp could only be replicated to 0 nodes instead of minReplication (=1).  There are 7 datanode(s) running and no node(s) are excluded in this operation.
	at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:1553)