[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on HDFS-826:
----------------------------------

Patch looks good to me. I question whether returning 0 for the case in between blocks is a good idea - this seems a bit confusing from the API user's perspective. Since it is well documented it may not be an issue, but I wonder if it would make more sense to actually return the intended replication in this case.

> Allow a mechanism for an application to detect that datanode(s)  have died in the write pipeline
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-826
>                 URL: https://issues.apache.org/jira/browse/HDFS-826
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: ReplicableHdfs.txt, ReplicableHdfs2.txt, ReplicableHdfs3.txt
>
>
> HDFS does not replicate the last block of the file that is being currently written to by an application. Every datanode death in the write pipeline decreases the reliability of the last block of the currently-being-written block. This situation can be improved if the application can be notified of a datanode death in the write pipeline. Then, the application can decide what is the right course of action to be taken on this event.
> In our use-case, the application can close the file on the first datanode death, and start writing to a newly created file. This ensures that the reliability guarantee of a block is close to 3 at all time.
> One idea is to make DFSOutoutStream. write() throw an exception if the number of datanodes in the write pipeline fall below minimum.replication.factor that is set on the client (this is backward compatible).

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