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

Zhe Zhang commented on HDFS-9924:
---------------------------------

My 2 cents:

I think the async feature should be done in a feature branch. As [~andrew.wang] 
said above and [~cmccabe] mentioned on the dev@ maillist, the overhead of using 
a feature branch (especially in this case where most changes are new code) is 
pretty minimum.

The only valid concern against a feature branch is that without an actual 
release, we will get less testing coverage from downstream projects. But the 
experience from EC is that if an advanced user wants to test a feature, he/she 
will just spend a little more time to build from the source code of the feature 
branch. This overhead is less significant compared with the degraded user 
experience if we release a set of APIs in alpha0 and change them in a later 
release, say alpha1. I think the async feature is attractive enough for at 
least a few downstream projects to try from feature branch.

> [umbrella] Asynchronous HDFS Access
> -----------------------------------
>
>                 Key: HDFS-9924
>                 URL: https://issues.apache.org/jira/browse/HDFS-9924
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Xiaobing Zhou
>         Attachments: AsyncHdfs20160510.pdf
>
>
> This is an umbrella JIRA for supporting Asynchronous HDFS Access.
> Currently, all the API methods are blocking calls -- the caller is blocked 
> until the method returns.  It is very slow if a client makes a large number 
> of independent calls in a single thread since each call has to wait until the 
> previous call is finished.  It is inefficient if a client needs to create a 
> large number of threads to invoke the calls.
> We propose adding a new API to support asynchronous calls, i.e. the caller is 
> not blocked.  The methods in the new API immediately return a Java Future 
> object.  The return value can be obtained by the usual Future.get() method.



--
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