hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iyappan Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-788) Datanode behaves badly when one disk is very low on space
Date Wed, 16 Dec 2009 07:10:18 GMT

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

Iyappan Srinivasan commented on HDFS-788:
-----------------------------------------

Please also look at MAPREDUCE-1296, which is  also a  similar sort of issue.

> Datanode behaves badly when one disk is very low on space
> ---------------------------------------------------------
>
>                 Key: HDFS-788
>                 URL: https://issues.apache.org/jira/browse/HDFS-788
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>            Reporter: Todd Lipcon
>
> FSDataset.getNextVolume() uses FSVolume.getAvailable() to determine whether to allocate
a block on a volume. This doesn't factor in other in-flight blocks that have been "promised"
space on the volume. The resulting issue is that, if a volume is nearly full but not full,
multiple blocks will be allocated on that volume, and then they will all hit "Out of space"
errors during the write.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message