[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336976#comment-15336976
]
Arpit Agarwal edited comment on HDFS-9924 at 6/17/16 9:26 PM:
--------------------------------------------------------------
Hi [~andrew.wang], Jitendra's proposal to revert the API while we continue the
discussion sounds like a reasonable compromise. I don't think a feature branch
buys us anything here. Our bylaws state - _Significant, pervasive features are
often developed in a speculative branch of the repository_ - and these changes
meet neither bar. Please consider holding off on your proposed revert. I will
take a look at HDFS-10538 which reverts the API and commit it within a couple
of days.
was (Author: arpitagarwal):
Hi [~andrew.wang], Jitendra's proposal to revert the API while we continue the
discussion sounds like a reasonable compromise. I don't think a feature branch
buys us anything here. Our bylaws state - _Significant, pervasive features are
often developed in a speculative branch of the repository_ - and these changes
meet neither bar. Please consider holding off on your proposed revert. I will
take a look at HADOOP-10538 which reverts the API and commit it within a couple
of days.
> [umbrella] Nonblocking 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: Async-HDFS-Performance-Report.pdf, AsyncHdfs20160510.pdf
>
>
> This is an umbrella JIRA for supporting Nonblocking 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 nonblocking 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]
