[
https://issues.apache.org/jira/browse/METRON-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940323#comment-15940323
]
ASF GitHub Bot commented on METRON-796:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/488
I agree the topologies should run as the metron user, but this is just to
get things back in a working state again (and it already used to be this way,
so this isn't opening things up more than it was a couple weeks ago).
I actually thought there was a separate Jira for running as the Metron
user, but the one I was thinking of is
https://issues.apache.org/jira/browse/METRON-349. The ticket should really be
to consolidate everything under the metron user with appropriate ownership. I
don't have a preference for updating that ticket or closing it as a new one
(and I'm not sure which the community would prefer).
> 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)
