hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9023) When NN is not able to identify DN for replication, reason behind it can be logged
Date Thu, 28 Dec 2017 19:58:00 GMT

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

Xiao Chen updated HDFS-9023:
----------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.1
                   2.9.1
                   2.10.0
                   3.1.0
           Status: Resolved  (was: Patch Available)

Precommit failures look unrelated.

Pushed this to trunk, branch-3.0, branch-2 and branch-2.9, to match HDFS-11494.

Thanks for reporting the issue and the reviews, [~surendrasingh]!

> When NN is not able to identify DN for replication, reason behind it can be logged
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-9023
>                 URL: https://issues.apache.org/jira/browse/HDFS-9023
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client, namenode
>    Affects Versions: 2.7.1
>            Reporter: Surendra Singh Lilhore
>            Assignee: Xiao Chen
>            Priority: Critical
>             Fix For: 3.1.0, 2.10.0, 2.9.1, 3.0.1
>
>         Attachments: HDFS-9023.01.patch, HDFS-9023.02.patch, HDFS-9023.03.patch, HDFS-9023.branch-2.patch
>
>
> 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.
> {noformat}
> 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)

> {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


Mime
View raw message