Cloudera Docs

Known issues in Streams Messaging Manager

Learn about the known issues for Streams Messaging Manager in Cloudera Runtime 7.2.7.

OPSAPS-59553: SMM's bootstrap server config should be updated based on Kafka's listeners

SMM does not show any metrics for Kafka or Kafka Connect when multiple listeners are set in Kafka.

Workaround: SMM cannot identify multiple listeners and still points to bootstrap server using the default broker port (9093 for SASL_SSL). You would have to override bootstrap server URL (hostname:port as set in the listeners for broker). Add the bootstrap server details in SMM safety valve in the following path:
Cloudera Manager > SMM > Configuration > Streams Messaging Manager Rest Admin Server Advanced Configuration Snippet (Safety Valve) for streams-messaging-manager.yaml > Add the following value for bootstrap servers>Save Changes > Restart SMM.
streams.messaging.manager.kafka.bootstrap.servers=<comma-separated list of brokers>
OPSAPS-59597: SMM UI logs are not supported by Cloudera Manager

Cloudera Manager does not display a Log Files menu for SMM UI role (and SMM UI logs cannot be displayed in the Cloudera Manager UI) because the logging type used by SMM UI is not supported by Cloudera Manager.

Workaround: View the SMM UI logs on the host.
OPSAPS-59828: SMM cannot connect to Schema Registry when TLS is enabled

When TLS is enabled, SMM by default cannot properly connect to Schema Registry.

As a result, when viewing topics in the SMM Data Explorer with the deserializer key or value set to Avro, the following error messages are shown:
  • Error deserializing key/value for partition [***PARTITION***] at offset [***OFFSET***]. If needed, please seek past the record to continue consumption.
  • Failed to fetch value schema versions for topic : '[***TOPIC**]'.
In addition, the following certificate error will also be present the SMM log:
  • javax.net.ssl.SSLHandshakeException: PKIX path building failed:...
Workaround: Additional security properties must be set for SMM.
  1. In Cloudera Manager, select the SMM service.
  2. Go to Configuration.
  3. Find and configure the SMM_JMX_OPTS property.
    Add the following JVM SSL properties:
    • Djavax.net.ssl.trustStore=[***SMM TRUSTSTORE LOCATION***]
    • Djavax.net.ssl.trustStorePassword=[***PASSWORD***]
OPSAPS-59124: Kafka, SMM, and SRM fail to start when there are multiple Ranger Admin roles running
If there are multiple Ranger Admin roles configured in a cluster, Kafka cannot create the Kafka resource based services in Ranger, which are required for authorization. If the resource based services are missing, the Kafka, SMM, and SRM services will fail to start.
Workaround:
  1. In Cloudera Manager, select the Kafka service.
  2. Go to Configuration.
  3. Find the Kafka Broker Environment Advanced Configuration Snippet (Safety Valve) property and add the following:
    RANGER_REST_URL=[***RANGER ADMIN HOST***]:[***RANGER ADMIN PORT***]
    • Replace [***RANGER ADMIN HOST***] with the hostname where a Ranger Admin service role is deployed. You can find the hostname by going to Ranger > Instances. The hostname is displayed in the Hostname column next to Ranger Admin. Choose one of the available Ranger Admin instances.
    • Replace [***RANGER ADMIN PORT***] with the port used by the Ranger Admin service role. The port is specified in the Admin HTTP Port or Admin HTTPS port Ranger property. Which port is used depends on whether SSL is enabled for Ranger Admin.
  4. Click Save Changes.
  5. Restart Kafka.
  6. Restart SMM and SRM.