[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316544#comment-15316544
]
Jitendra Nath Pandey commented on HDFS-9924:
--------------------------------------------
[~aw], yes this is a new feature, but not very large. The work is already
complete and the functionality works in its current form already. Only one
point of discussion was to enhance the current API to support callbacks as
well, which was accepted as a useful enhancement that many people need.
Also, the earlier objection was raised for only 2.8 release, but patches were
reverted from all the branches arbitrarily.
I propose following next steps to make quick progress here:
1) The design should be enhanced to support callback in the API. A jira should
be created as a subtask here for the change.
2) The jira may be marked a blocker for 2.8 release. However, It is release
manager's discretion to decide what is a blocker. When we get close to 2.8 and
it is still not resolved the feature can be disabled or reverted, again
depending on release manager's decision. The usual practice is that release
manager prods the developers and they try to expedite the fixes and
improvements for the release. As far as I understand this is not going to be a
complicated improvement to add.
Lets just expedite to fix (1) above, and put this behind us.
> [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]
