[
https://issues.apache.org/jira/browse/HADOOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601996#action_12601996
]
dhruba borthakur commented on HADOOP-3177:
------------------------------------------
The semantics of FileSystem.fsync is that the system makes every effort to put
data on persistent storage. In the case of local file system, it will invoke
the sync on the local file system. In the case of DFS, it will ensure that data
has been flushed to OS buffers on all datanode(s) in the pipeline.
If a file-system does not support fsync, then it should be a no-op rather than
an exception.This is similar to other calls like setReplication which returns
success on local file systems even though there isn't any replication for local
file system.
> Expose DFSOutputStream.fsync API though the FileSystem interface
> ----------------------------------------------------------------
>
> Key: HADOOP-3177
> URL: https://issues.apache.org/jira/browse/HADOOP-3177
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> In the current code, there is a DFSOutputStream.fsync() API that allows a
> client to flush all buffered data to the datanodes and also persist block
> locations on the namenode. This API should be exposed through the generic API
> in the org.hadoop.fs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
