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

Jing Zhao commented on HDFS-4213:
---------------------------------

Thanks for the comments Todd. To allow hflush() to update the NN's metadata is 
also in the plan but I plan to do that in an separate jira so as to make the 
backport easier (considering branch-1 only has hflush semantic).

The enum improvement looks very good. I will update the patch to address the 
comment.
                
> When the client calls hsync(), allows the client to update the file length in 
> the NameNode
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4213
>                 URL: https://issues.apache.org/jira/browse/HDFS-4213
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 3.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-4213.001.patch, HDFS-4213.002.patch, 
> HDFS-4213.003.patch
>
>
> As per discussion in HDFS-3960 and HDFS-2802, when clients that need strong 
> consistency update the file length at the NameNode, a special sync is 
> required for getting the length of the being written files when snapshots are 
> taken for these files. This jira implements this sync-with-updating-length by 
> 1) calling ClientProtocol#fsync(), and 2) adding a new field to 
> ClientProtocol#fsync() to indicate the length information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to