[
https://issues.apache.org/jira/browse/HADOOP-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662500#action_12662500
]
Doug Cutting commented on HADOOP-4998:
--------------------------------------
> If we have access to poll(), we would just us that for Hadoop's blocking IO
> on non-blocking sockets
Should each of these be a separate issue?
We currently have an optional libhadoop. If we want to add more to it, I can
see proceeding in one of a few ways:
- adding more optional optimizations there, on a case-by-case basis; or
- replace all shell access with native code, replacing the reliance on bash
with reliance on a native library.
But adding a few more optional optimizations doesn't seem like a single
coherent issue and would better be addressed by more specific jiras, no?
> Implement a native OS runtime for Hadoop
> ----------------------------------------
>
> Key: HADOOP-4998
> URL: https://issues.apache.org/jira/browse/HADOOP-4998
> Project: Hadoop Core
> Issue Type: New Feature
> Components: native
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.21.0
>
>
> It would be useful to implement a JNI-based runtime for Hadoop to get access
> to the native OS runtime. This would allow us to stop relying on exec'ing
> bash to get access to information such as user-groups, process limits etc.
> and for features such as chown/chgrp (org.apache.hadoop.util.Shell).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
