Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Re: [jira] [Created] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails


Copy link to this message
-
RE: [jira] [Created] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails
UNSUBSCRIBE

Vivek Durairaj

-----Original Message-----
From: Brent Nikolaus [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 12, 2013 1:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [jira] [Created] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

UNSUBSCRIBE
On Fri, Jul 20, 2012 at 6:42 AM, Kihwal Lee (JIRA) <[EMAIL PROTECTED]> wrote:

> Kihwal Lee created HADOOP-8611:
> ----------------------------------
>
>              Summary: 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: 2.0.0-alpha, 0.23.0, 1.0.3
>             Reporter: Kihwal Lee
>             Assignee: Kihwal Lee
>              Fix For: 1.1.1, 0.23.3, 3.0.0, 2.2.0-alpha
>
>
> 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:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.js
> pa For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
>
--
Brent Nikolaus
CISSP - LPT - CEH - CSFA - DFHI - ACE
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB