Troubleshooting

This section provides information about troubleshooting this release. It contains the following topics:

Enabling debug

Follow these steps to enable PSL and Java debug.

On the policy configuration of the Apache Kafka KM, in the KM Administration group, select the Logging check box.

The PSL debug log file is located at PATROL_HOME/log/kfk_<environment name>-<hostname>-<port>.kmlog

The Java debug log file is located at PATROL_HOME/kfk/log/java

Other issues

Apache Kafka KM does not monitor all the Brokers in the system

Ensure that you start the KM monitoring before running the Producer process, when you are monitoring a topic that does not exist. This action causes the topic to be created successfully with expected number of partitions. 

Java Producer process consumes high memory

When monitoring the Kafka environment with a large amount of Brokers, the Java Producer process might consume high memory.

To resolve the issue

Incorrect message time calculation

To resolve this issue synchronize time across the PATROL Agent system (UTC) and the Producer system to seconds precision.

Producer availability goes down when stopping one of the Brokers, and all producers stop collecting data

This might happen when one or more Brokers are unavailable. In this scenario, the consumer stops responding and the producer metrics are unavailable. To resolve this issue, restart the Broker.

Apache Kafka KM stops monitoring in the Kerberos environment

To resolve this issue:

• Ensure that the krb5 and the JAAS configuration files are built correctly

• Try using the krb5 and the JAAS configuration combinations, that is, kafka-console-producer or kafka-console-consumer that are available in KAFKA_HOME/bin location
  
  For Linux
  
  • • Export KAFKA_OPTS="-Djava.security.krb5.conf=<path to the krb5 file> -Djava.security.auth.login.config=<path to the JAAS file>"
    • Ensure that the Producer and the Consumer properties contain the following:
    • • security.protocol=SASL_PLAINTEXT
      • sasl.kerberos.service.name=<your service name>
  • • Run the producer as
      ./kafka-console-producer.sh --broker-list <BrokerHost:port> --topic <topic name> --producer.config=<path to producer property file>
    • Run the consumer as 
      ./kafka-console-consumer.sh --bootstrap-server <ZookeeperHost:port>--topic <topic name> --consumer.config=<path to consumer property file>
  
  For Windows

• • Set KAFKA_OPTS="-Djava.security.krb5.conf=<path to the krb5 file> -Djava.security.auth.login.config=<path to the JAAS file>"
  • Ensure that the Producer and the Consumer properties contain the following:
    
    • security.protocol=SASL_PLAINTEXT
    • sasl.kerberos.service.name=<your service name>

• • Run the producer as
    kafka-console-producer.bat --broker-list <BrokerHost:port> --topic <topic name> --producer.config=<path to producer property file>
  • Run the consumer as 
    kafka-console-consumer.bat --bootstrap-server <ZookeeperHost:port>--topic <topic name> --consumer.config=<path to consumer property file>