[
https://issues.apache.org/jira/browse/METRON-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979064#comment-15979064
]
ASF GitHub Bot commented on METRON-861:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/534
Looks good to me. This should be generally useful, even outside of the
jaas use case.
Would it make sense to namespace the JVMFLAGS environment variable so it's
specific to Metron? Not sure it matters much but it would make it more
consistent with other environment variables we use.
> Allow JVM args to be passed to CLI utilities
> --------------------------------------------
>
> Key: METRON-861
> URL: https://issues.apache.org/jira/browse/METRON-861
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> This is motivated by the fact that if one sets the acl's on the znodes that
> metron creates (e.g. /metron/topology/global) to read/write by metron (from
> the zkcli `setAcl /metron/topology/global sasl:metron:crwda`), then
> permissions prohibit the CLI tools from functioning because the JAAS config
> is not loaded.
> This JIRA allows users to pass java properties to the CLI tools. While
> important for Kerberos, it's useful in general if one needs to adjust the
> heap required, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
