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

Hadoop QA commented on HDFS-16243:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime ||  Logfile || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue}{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m 12s{color} 
| {color:red}{color} | {color:red} HDFS-16243 does not apply to trunk. Rebase 
required? Wrong Branch? See 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-16243 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/13034674/HDFS-16243.0.patch |
| Console output | 
https://ci-hadoop.apache.org/job/PreCommit-HDFS-Build/720/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org |


This message was automatically generated.



> The available disk space is less than the reserved space, and no log message 
> is displayed
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-16243
>                 URL: https://issues.apache.org/jira/browse/HDFS-16243
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.7.2
>            Reporter: Hualong Zhang
>            Priority: Major
>             Fix For: 2.7.2
>
>         Attachments: HDFS-16243.0.patch
>
>
> When I submitted a task to the hadoop test cluster, it appeared "could only 
> be replicated to 0 nodes instead of minReplication (=1)"
> I checked the namenode and datanode logs and did not find any error logs. It 
> was not until the use of dfsadmin -report that the available capacity was 0 
> and I realized that it may be a configuration problem.
> Checking the configuration found that the value of the 
> "dfs.datanode.du.reserved" configuration is greater than the available disk 
> space of HDFS, which caused this problem
> It seems that there should be some warnings or errors in the log.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to