[
https://issues.apache.org/jira/browse/METRON-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941103#comment-15941103
]
ASF GitHub Bot commented on METRON-796:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/488
@mattf-horton Permissions on the other items are generally 775, so they can
be read as needed (and should be scaled back once we have everything lined up
with the user as @simonellistonball mentions). I just wanted to touch things as
little as possible to get them back in a working state.
We should either expand out or replace METRON-349 (including closing off
permissions) as the actual solution to the problem.
> 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)
