[
https://issues.apache.org/jira/browse/METRON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088154#comment-16088154
]
ASF GitHub Bot commented on METRON-1031:
----------------------------------------
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/647#discussion_r127555429
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/templates/metron.j2
---
@@ -37,3 +37,5 @@ SECURITY_ENABLED={{security_enabled|lower}}
{% endif %}
{% if metron_keytab_path is defined
%}METRON_SERVICE_KEYTAB="{{metron_keytab_path}}"
{% endif %}
+KAFKA_SECURITY_PROTOCOL="{{kafka_security_protocol}}"
+PARSER_TOPOLOGY_OPTIONS="/home/metron/.storm/storm.config"
--- End diff --
I think that's fine. If you really wanted it to mirror the implementation
in the MPack, you could do:
`PARSER_TOPOLOGY_OPTIONS="/home/{{metron_user}}/.storm/storm.config"`
> Management UI Cannot Start Topologies in Kerberized Environment
> ---------------------------------------------------------------
>
> Key: METRON-1031
> URL: https://issues.apache.org/jira/browse/METRON-1031
> Project: Metron
> Issue Type: Bug
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> The Metron Management UI cannot start topologies in a kerberized environment.
> This includes the parser, indexing, and enrichment topologies.
> It seems that Metron REST does not pass "-ksp" to the start topology
> commands. As a result, topologies that are started with the Management UI
> cannot start a producer against a kerberized Kafka.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
