[
https://issues.apache.org/jira/browse/METRON-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940429#comment-15940429
]
ASF GitHub Bot commented on METRON-797:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/490
If you want to review just this work independent of 793 prior to 793
getting merged, you can find the commits:
*
[here](https://github.com/apache/incubator-metron/pull/490/commits/5e614efd861a1d059e04ef64914fc185b111e4b6)
Also, I still owe some doc changes around kerberizing vagrant and the CLI
change to the `start_parser_topology.sh` script.
> Pass security.protocol and enable auto-renew for the storm topologies
> ---------------------------------------------------------------------
>
> Key: METRON-797
> URL: https://issues.apache.org/jira/browse/METRON-797
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
>
> METRON-793 migrated the storm topologies to the storm-kafka-client spout,
> which supports kerberos. To complete the kerberos work on the existing
> topologies, we need to be able to enable the spouts and kafka writers to use
> security protocols other than PLAINTEXT. Also, enabling auto-renew plugins
> for storm will enable the topologies to run for extended durations in a
> kerberized cluster.
> NOTE: This does not encompass MPack changes to enable kerberos or fix the
> sensors to work with a kerberized kafka. That would be follow-on work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
