hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3574) Better Datanode DiskOutOfSpaceException handling.
Date Wed, 03 Dec 2008 04:58:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652684#action_12652684

Suresh Srinivas commented on HADOOP-3574:

Should we create another jira to recover form this condition. We could use mechanism similar
to balancer to move some blocks to other datanodes to free up space? Datanodes could also
indicate this condition to namenode and trigger freeing up space by moving blocks. Alternatively,
this could also be done proactively by the namenode when the free space reported by the datanode
(during heartbeat) goes below certain threshold. This will improve robustness.

> Better Datanode DiskOutOfSpaceException handling.
> -------------------------------------------------
>                 Key: HADOOP-3574
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3574
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Tsz Wo (Nicholas), SZE
> When a datanode ran out of disk space, it throws DiskOutOfSpaceException internally.
 However, it does not notify the writing client about the exception.  As a result, the client
will wait until socket timeout.

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

View raw message