Known issues in Streams Messaging Manager

Learn about the known issues in Streams Messaging Manager, the impact or changes to the functionality, and the workaround.

CDPD-39313: Some numbers are not rendered properly in SMM UI

Very large numbers can be imprecisely represented on the UI. For example, bytes larger than 8 petabytes would lose precision.

None.

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.

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 support the log type used by SMM UI.

View the SMM UI logs on the host.

CDPD-88488: The Streams Messaging Manager server fails to start if its keystore password starts with a special character or includes quotation marks

Ensure that the Streams Messaging Manager server keystore password meets the following requirements:

• It does not start with a special character. Special characters are permitted in other positions.
• It does not contain quotation marks (single or double) anywhere.

CDPD-76375: Topic column name is incorrect in the replications table

On the Cluster Replications page, in the replications table, the topic column name is incorrectly named Source Topic Name instead of Target Topic Name. This means that the Source Topic Name column currently shows the topic name on the target cluster, instead of the topic name on the source cluster.