[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317717#comment-15317717
]
stack commented on HDFS-9924:
-----------------------------
Ugh. I meant to say, we risk having different 'async' API/implementations if we
piecemeal the implementation ahead of our figuring a general approach for
async'ing the Filesystem. What is committed currently is inadequate according
to the discussion so far missing callback. Retrofitting callback on Future, as
I understand it, will require a different implementation; therefore the commits
are premature. Revert in the meantime seems like the right thing to do.
bq. I'm much more worried about API correctness.... Waiting a while to actually
let more folks play with it before pushing it into a release (including the 3.x
release that we're working to cut from trunk) just seems like an obvious,
common sense thing to do.
Above makes sense to me.
> [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]
