hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9924) [umbrella] Nonblocking HDFS Access
Date Thu, 16 Jun 2016 19:22:05 GMT

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

Jitendra Nath Pandey commented on HDFS-9924:

  The lack of consensus is only for the API. The underlying implementation is useful for any
API we choose. I will suggest to create a patch to remove only the AsyncDistributedFileSystem
API. I can do that if thats an agreeable approach. 

[~andrew.wang], I think you earlier mentioned that you are ok to move out only the API. I
would rather revert only the API, or move it to a test and that will avoid the overhead of
a branch. 

The other proposal in  HDFS-10535, for non blocking hdfs access, should not implement the
file system interface, therefore it is not just a rename. If that is acceptable, we can have
the Async API only in the trunk. At this point, I think it will be lot easier to build a consensus
first in trunk.

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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message