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

Tsz Wo Nicholas Sze commented on HDFS-9924:
-------------------------------------------

> It's pretty obvious this should be going into a feature branch and requiring 
> a branch-merge vote. ...  I really wish the PMC was more actively watching 
> what is actually going on in the source tree because this type of behavior 
> ultimately hurts stability.

We did not need a branch here since, as mentioned before, this change was 
adding mostly new code but not changing existing code much.  Therefore, this 
feature won't hurt stability.

You might be upset by other features such as HDFS symlink.  I am sorry about 
that.  I believe the PMC is already closely watching the commits.  In case you 
find any problems, please rise your concern to the PMC.

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