Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 479E2DD30 for ; Wed, 15 Aug 2012 14:18:39 +0000 (UTC) Received: (qmail 32909 invoked by uid 500); 15 Aug 2012 14:18:39 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 32830 invoked by uid 500); 15 Aug 2012 14:18:38 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 32821 invoked by uid 99); 15 Aug 2012 14:18:38 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 14:18:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 60C652C5BE9 for ; Wed, 15 Aug 2012 14:18:38 +0000 (UTC) Date: Thu, 16 Aug 2012 01:18:38 +1100 (NCT) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1682477346.13656.1345040318397.JavaMail.jiratomcat@arcas> In-Reply-To: <1400592827.81708.1342791755993.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435141#comment-13435141 ] Hadoop QA commented on HADOOP-8611: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12541046/HADOOP-8611.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests in hadoop-common-project/hadoop-common: org.apache.hadoop.ha.TestZKFailoverController +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1304//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1304//console This message is automatically generated. > 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.1.1, 0.23.3, 3.0.0, 2.2.0-alpha > > Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira