[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336343#comment-15336343
]
Jitendra Nath Pandey commented on HDFS-9924:
--------------------------------------------
The overhead of feature branch is not just git work, it is also about review
for the code at merge time, that is already in trunk. Undoing and redoing that
work is redundant. Also, we need to periodically merge from trunk to the
feature branch and resolve conflicts if any. Therefore, smaller the delta in
the feature branch easier it is to manage.
The feature branch will still be useful for the continued work on the API.
HDFS-10538 reverts AsyncDFS, we should put that reverted code on the feature
branch, and any further API development can be continued there. That way, the
feature branch will have a very small delta, and the desired goal of moving API
development to the feature branch will be achieved. At this point, committing
HDFS-10538 is much simpler effort to achieve that. I can quickly commit
HDFS-10538, if you agree.
bq. Benefits of AsyncDFS to a test package
This is equivalent to removing it, but helps us preserve the unit tests that
make it easier to maintain rest of the code.
> [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]
