You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Matt Foley (JIRA)" <ji...@apache.org> on 2013/05/06 05:30:18 UTC
[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based
implementation when JNI-based users-group mapping fails
[ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated HADOOP-8611:
-------------------------------
Fix Version/s: 1.2.0
> Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-8611
> URL: https://issues.apache.org/jira/browse/HADOOP-8611
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha
> Reporter: Kihwal Lee
> Assignee: Robert Parker
> Fix For: 1.2.0, 0.23.3, 2.0.2-alpha
>
> Attachments: HADOOP-8611-branch1.patch, HADOOP-8611-branch1.patch, HADOOP-8611.patch, HADOOP-8611.patch, HADOOP-8611.patch
>
>
> When the JNI-based users-group mapping is enabled, the process/command will fail if the native library, libhadoop.so, cannot be found. This mostly happens at client-side where users may use hadoop programatically. Instead of failing, falling back to the shell-based implementation will be desirable. Depending on how cluster is configured, use of the native netgroup mapping cannot be subsituted by the shell-based default. For this reason, this behavior must be configurable with the default being "disabled".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira