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

Hadoop QA commented on HDFS-14616:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  8s{color} 
| {color:red} HDFS-14616 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-14616 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12975366/HDFS-14616-v3.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/27275/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Add the warn log when the volume available space isn't enough
> -------------------------------------------------------------
>
>                 Key: HDFS-14616
>                 URL: https://issues.apache.org/jira/browse/HDFS-14616
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>    Affects Versions: 2.7.2
>            Reporter: liying
>            Assignee: liying
>            Priority: Minor
>         Attachments: HDFS-14616-v1.patch, HDFS-14616-v2.patch, 
> HDFS-14616-v3.patch
>
>
> In the hadoop2 version, there is no warning log that the disk is not 
> available when using the disk. Therefore, the datanode log cannot be used to 
> check if the disk is not available ata certain time or for other problems.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to