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

stack commented on HADOOP-12910:
--------------------------------

Back now [~cnauroth]

bq. ...whereas the scope of this issue has focused on asynchronous NameNode 
metadata operations....

The discussion in here is more broad than just NN metadata operations. The 
summary and description would seem to encourage how we will add async to 
FileSystem generally. It seems like a good thing to nail given async is coming 
up in a couple of areas ([~Apache9]'s file ops and these NN calls). They should 
all align on their approach I'd say.

Regards a writeup, [~Apache9] has revived HDFS-916 and added doc on what is 
wanted doing async file ops. High-level, we want to be able to consume an HDFS 
API async, in an event-driven way. A radical experiment that totally replaces 
dfsclient with a simplified, bare-bones implementation that does the minimal 
subset necessary for writing HBase WALs (HBASE-14790) allows us write much 
faster while using less resources. The implementation also does fan-out rather 
than pipeline. This put together with it being barebones -- e.g. we do not want 
to trigger pipeline recovery, it takes too long, if it works -- muddies the 
compare but the general drift is plain.

> Add new FileSystem API to support asynchronous method calls
> -----------------------------------------------------------
>
>                 Key: HADOOP-12910
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12910
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Xiaobing Zhou
>         Attachments: HADOOP-12910-HDFS-9924.000.patch, 
> HADOOP-12910-HDFS-9924.001.patch, HADOOP-12910-HDFS-9924.002.patch
>
>
> Add a new API, namely FutureFileSystem (or AsynchronousFileSystem, if it is a 
> better name).  All the APIs in FutureFileSystem are the same as FileSystem 
> except that the return type is wrapped by Future, e.g.
> {code}
>   //FileSystem
>   public boolean rename(Path src, Path dst) throws IOException;
>   //FutureFileSystem
>   public Future<Boolean> rename(Path src, Path dst) throws IOException;
> {code}
> Note that FutureFileSystem does not extend FileSystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to