Community Articles

Find and share helpful community-sourced technical articles.
Celebrating as our community reaches 100,000 members! Thank you!
Labels (1)

Short Description:

This article walks you through how to deploy a custom parser on kerberized cluster in Metron .


When adding a net new data source to Metron, the first step is to create kafka topic 'sensor_topic' to push the events from the new telemetry data source into Metron. The second step is to configure Metron to parse the telemetry data source so that downstream processing can be done on it. This wiki doc will walk you through how to perform both of these steps.

In this article I have added steps to perform the same operation on a kerberised cluster. On kerberised cluster we need to add the required ACL's to metron user and parser group for the created topic. Also we need to provide the storm authorization while deploying the topology.

1. Switch to the kafka user .

su kafka

2. create sensor topic

/usr/hdp/current/kafka-broker/bin/ --zookeeper $ZOOKEEPER --create --topic sensor_topic_name --partitions 1 --replication-factor 1 

3. Add required ACL to metron user

/usr/hdp/current/kafka-broker/bin/ --authorizer-properties zookeeper.connect=nat-r7-hets-metron-1:2181 --add  --allow-principal User:metron --operation All --topic 'sensor_topic_name' --cluster 

4. Add required ACL to group

/usr/hdp/current/kafka-broker/bin/ --authorizer  --authorizer-properties zookeeper.connect=$ZOOKEEPER --add --allow-principal User:metron  --group sensor_topic_name_parser 

5. Switch to the metron user and acquire a Kerberos ticket for the metron principal.

su metron
kinit -kt /etc/security/keytabs/metron.headless.keytab metron@EXAMPLE.COM 

6. Deploy the new Parser Topology

/usr/hcp/ -k $KAFKA_BROKER -z $ZOOKEEPER -s sensor_name -ksp PLAINTEXTSASL -e ~metron/.storm/storm.config
Version history
Last update:
‎07-20-2018 09:17 AM
Updated by: