[ 
https://issues.apache.org/jira/browse/METRON-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940841#comment-15940841
 ] 

ASF GitHub Bot commented on METRON-796:
---------------------------------------

Github user justinleet commented on a diff in the pull request:

    https://github.com/apache/incubator-metron/pull/488#discussion_r107965896
  
    --- Diff: 
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/params/params_linux.py
 ---
    @@ -39,7 +39,7 @@
     tmp_dir = Script.get_tmp_dir()
     
     hostname = config['hostname']
    -metron_group = config['configurations']['cluster-env']['metron_group']
    +hadoop_group = config['configurations']['cluster-env']['user_group']
    --- End diff --
    
    Updated with a comment to clarify things a bit.  Let me know if you think 
there's anything else we want to add or clarify.


> Mpack uses wrong group for owning HDFS directories
> --------------------------------------------------
>
>                 Key: METRON-796
>                 URL: https://issues.apache.org/jira/browse/METRON-796
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Justin Leet
>            Assignee: Justin Leet
>
> org.apache.hadoop.security.AccessControlException: Permission denied: 
> user=storm, access=WRITE, 
> inode="/apps/metron/indexing/indexed/snort/enrichment-null-0-0-1490305873514.json":metron:metron:drwxrwx
> The group got changed a bit ago from cluster_env.user_group (hadoop) to 
> cluster_env.metron_group (metron).  However, because everything right now 
> runs as the storm user (which is in the hadoop group), it doesn't have perms 
> to write anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to