hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10388) Pure native hadoop client
Date Wed, 12 Mar 2014 18:20:46 GMT

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

Colin Patrick McCabe commented on HADOOP-10388:

I was going to post an RPC client using libuv.  libuv is nice because it's cross-platform
(including UNIX and Windows), MIT-licensed, and has platform wrapper functions like uv_thread_create
and uv_mutex_lock, etc. so we won't have to write our own platform stuff for Linux, Windows,
etc.  libuv also supports async (TCP) I/O, which I would like to have in the RPC client to
provide flexibility.

I think the best structure is to start with the RPC library in hadoop-common, and then perhaps
work on a native HDFS client that uses it in hadoop-hdfs.  There will be a lot to do there
and we can split up the work.  I'm going to try to post something for RPC by next week.

> Pure native hadoop client
> -------------------------
>                 Key: HADOOP-10388
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10388
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Binglin Chang
>            Assignee: Colin Patrick McCabe
> A pure native hadoop client has following use case/advantages:
> 1.  writing Yarn applications using c++
> 2.  direct access to HDFS, without extra proxy overhead, comparing to web/nfs interface.
> 3.  wrap native library to support more languages, e.g. python
> 4.  lightweight, small footprint compare to several hundred MB of JDK and hadoop library
with various dependencies.

This message was sent by Atlassian JIRA

View raw message