[ https://issues.apache.org/jira/browse/HDFS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HDFS-788. ----------------------------------- Resolution: Fixed This has likely been fixed. > 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: datanode > 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 was sent by Atlassian JIRA (v6.2#6252)