[
https://issues.apache.org/jira/browse/HADOOP-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663825#action_12663825
]
Marco Nicosia commented on HADOOP-4998:
---------------------------------------
I am really close to raising this to a blocker for Hadoop 0.18.3, BUT, I'm
worried this isn't the right ticket. The symptom we're struggling with is that
when a primary or secondary namenode wants to fork to run bash, it requires
double memory than what it's currently using.
I don't care if the solution is JNI or some IPC to some other process to run
shell processes, but it's an inconvenient issue to work around. Is this the
right ticket to take on fixing that, or should we create a different JIRA?
> 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.
