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

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

Github user mattf-horton commented on the issue:

    https://github.com/apache/incubator-metron/pull/488
  
    Thanks.  Looks okay to me now, for the intended purpose.  +0 due to Simon's 
concerns; I'd prefer someone with more experience in Metron give you the plus 
one.
    
    Regarding @simonellistonball 's comments:
    The prior assignment of group ownership as `metron_group` in 
enrichment_commands.py, line 114, and indexing_commands.py, line 104, dates 
from the commit for 
    * [METRON-671 Refactor existing Ansible deployment to use Ambari MPack 
(dlyle via 
justinleet)#436](https://github.com/justinleet/incubator-metron/commit/68a334a8717d2a6b82f7f9651c57bc75e256ba97)
    Prior to PR#436 they were both set to `user_group`.
    
    @dlyle65535 are you okay with setting these back to `user_group`, as they 
were before?
    ie do you agree with @justinleet 's reasoning?  Thanks.
    
    @justinleet , you say: "Other items, such as configs and installation 
files, were just left as the metron group."  Why is this okay?  Don't the 
topologies have to read config files too?  Thanks.


> 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