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 "Kihwal Lee (JIRA)" <ji...@apache.org> on 2012/07/20 15:42:35 UTC

[jira] [Created] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

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.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy closed HADOOP-8611.
---------------------------------

    
> 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: 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

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438660#comment-13438660 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #350 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/350/])
    svn merge -c 1375221 FIXES: HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375224)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375224
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Target Version/s: 0.23.3, 2.1.0-alpha
              Status: Patch Available  (was: Open)

This patch applies to trunk.  Once reviewed I will post the 1.0 patch
                
> 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: 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

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Joseph Evans updated HADOOP-8611:
----------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.1.1)
                   2.1.0-alpha
                   1.2.0
           Status: Resolved  (was: Patch Available)

Thanks Rob,

I checked this into trunk, branch-2, branch-2.1.0-alpha and branch-0.23.
                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435181#comment-13435181 ] 

Robert Parker commented on HADOOP-8611:
---------------------------------------

core-tests failures were time out issues, verified locally on trunk and my branch that TestZKFailoverController tests pass.
                
> 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Jason Lowe (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435187#comment-13435187 ] 

Jason Lowe commented on HADOOP-8611:
------------------------------------

TestZKFailoverController timing out is a known issue, see HADOOP-8591.
                
> 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438262#comment-13438262 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2636 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2636/])
    HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375221)

     Result = FAILURE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375221
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438222#comment-13438222 ] 

Hadoop QA commented on HADOOP-8611:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12541645/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 passed unit tests in hadoop-common-project/hadoop-common.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1330//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1330//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.2.0, 0.23.3, 2.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436028#comment-13436028 ] 

Robert Parker commented on HADOOP-8611:
---------------------------------------

Uploaded new patch, isolated the fallback functionality to 2 new specific classes which can be specified within the current configuration scheme. 
                
> 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, 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436060#comment-13436060 ] 

Hadoop QA commented on HADOOP-8611:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12541230/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/1319//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1319//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, 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438217#comment-13438217 ] 

Robert Joseph Evans commented on HADOOP-8611:
---------------------------------------------

It might be good to consider filing a separate JIRA to make the default groups implementation the JNI shell with fallback.
                
> 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-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438215#comment-13438215 ] 

Robert Joseph Evans commented on HADOOP-8611:
---------------------------------------------

+1 the changes look good I'll check it in.
                
> 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-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435202#comment-13435202 ] 

Robert Joseph Evans commented on HADOOP-8611:
---------------------------------------------

The code looks good, but I have a few comments.

 # There are tabs in the patch, please update it to use spaces instead.
 # The way the patch is getting the impl instance is very repetative.  I think it would be simpler to do the following {code}
Class<GroupMappingServiceProvider> clazz = conf.getClass(CommonConfigurationKeys.HADOOP_SECURITY_GROUP_MAPPING, 
                                 ShellBasedUnixGroupsMapping.class, 
                                 GroupMappingServiceProvider.class);
if (conf.getBoolean(CommonConfigurationKeys.HADOOP_SECURITY_GROUP_MAPPING_ALLOW_FALLBACK, false) &&
  !NativeCodeLoader.isNativeCodeLoaded()) {
  LOG.info("Falling back to Shell Based Groups");
  clazz = ShellBasedUnixGroupsMapping.class;
}
impl = ReflectionUtils.newInstance(clazz, conf);
{code}
 # It would be good to update ./hadoop-hdfs-project/hadoop-hdfs/src/main/docs/src/documentation/content/xdocs/hdfs_permissions_guide.xml with the new config option
 # Do we want to check explicitly for JniBasedUnixGroupsMapping and JniBasedUnixGroupsNetgroupMapping? or perhaps move some of this code over into those classes explicitly instead?  It seems like configuring LdapGroupsMapping with fallback enabled and non-native code would never work.  Also there would be issues with JniBasedUnixGroupsNetgroupMapping and fallback.  Is this the reason for having the fallback enable?
                
> 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436390#comment-13436390 ] 

Hadoop QA commented on HADOOP-8611:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12541277/HADOOP-8611-branch1.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 passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1321//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1321//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-branch1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438189#comment-13438189 ] 

Robert Parker commented on HADOOP-8611:
---------------------------------------

added a new patch for branch 1 to remove mvn references and added curly braces to if statement
added a new patch for trunk to add curly braces to if statement
                
> 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-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438671#comment-13438671 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Hdfs-trunk #1141 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1141/])
    HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375221)

     Result = FAILURE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375221
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438251#comment-13438251 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #2671 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2671/])
    HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375221)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375221
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438249#comment-13438249 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #2607 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2607/])
    HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375221)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375221
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438737#comment-13438737 ] 

Hudson commented on HADOOP-8611:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #1173 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1173/])
    HADOOP-8611. Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails (Robert Parker via bobby) (Revision 1375221)

     Result = FAILURE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375221
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/JniBasedUnixGroupsNetgroupMappingWithFallback.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupFallback.java

                
> 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.1.0-alpha, 3.0.0, 2.2.0-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Attachment: HADOOP-8611.patch
    
> 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, 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

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Attachment: HADOOP-8611-branch1.patch

Patch for branch-1.0.2
                
> 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-branch1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Attachment: HADOOP-8611.patch
    
> 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

        

[jira] [Commented] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438021#comment-13438021 ] 

Robert Joseph Evans commented on HADOOP-8611:
---------------------------------------------

I have two comments.

 # {code}if (LOG.isDebugEnabled())
      LOG.debug("Group mapping impl=" + impl.getClass().getName());
{code} needs curly braces around the if body.  
 # The 1.0 branch refers to running mvn test, but 1.0 does not support mvn.  Please either update them or remove them.

                
> 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-branch1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker reassigned HADOOP-8611:
-------------------------------------

    Assignee: Robert Parker  (was: Kihwal Lee)
    
> 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
>
>
> 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

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Attachment: HADOOP-8611.patch

added curly braces
                
> 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-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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HADOOP-8611) Allow fall-back to the shell-based implementation when JNI-based users-group mapping fails

Posted by "Robert Parker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Parker updated HADOOP-8611:
----------------------------------

    Attachment: HADOOP-8611-branch1.patch

removed mvn references
                
> 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-branch1.patch, HADOOP-8611-branch1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira