ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-11351) HdfsResource does not account for sticky bit
Date Sat, 23 May 2015 00:08:18 GMT


Hadoop QA commented on AMBARI-11351:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in contrib/fast-hdfs-resource.

Test results:
Console output:

This message is automatically generated.

> HdfsResource does not account for sticky bit
> --------------------------------------------
>                 Key: AMBARI-11351
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: contrib
>    Affects Versions: Ambari-2.1
>         Environment: Linux
>            Reporter: Shantanu Mundkur
>            Assignee: Shantanu Mundkur
>              Labels: patch
>             Fix For: Ambari-2.1
>         Attachments: AMBARI-11351.patch
> Specifying a mode of 01777 will result in an exception like:
> Exception in thread "main" java.lang.IllegalArgumentException: 1777
> at org.apache.hadoop.fs.permission.PermissionParser.<init>(
> at org.apache.hadoop.fs.permission.UmaskParser.<init>(
> at org.apache.hadoop.fs.permission.FsPermission.<init>(
> at org.apache.ambari.fast_hdfs_resource.Resource.setMode(
> at org.apache.ambari.fast_hdfs_resource.Runner.main(
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> at java.lang.reflect.Method.invoke(
> at
> at org.apache.hadoop.util.RunJar.main(
> In fast_hdfs_resource, setMode is used to set the permissions on the Resource object
using the specified mode. Passing in the mode as a string for FsPermission is what results
in the problem because the constructor that is used with string as argument uses the UmaskParser.
Umask values are slightly different from standard modes as they cannot specify t (sticky bit)
or X.
> Passing in the argument as a short is probably what is needed here to enable using the
FsPermission code that accounts for the sticky bit.

This message was sent by Atlassian JIRA

View raw message