Known issues and technical limitations for Streams Messaging Manager are
addressed in Cloudera Runtime 7.3.2, its service packs, and cumulative
hotfixes.
Known Issues identified in Cloudera Runtime 7.3.2
- Alert policies based on the LEADER ELECTION PER SEC
attribute do not trigger
- 7.3.2
- If the monitored Kafka cluster is running in KRaft
mode, alert policies based on the LEADER ELECTION PER
SEC alert policy attribute will not trigger because the
underlying metrics are not available from Kafka. The attribute remains
visible and selectable in Streams Messaging Manager even if the
monitored cluster is running in KRaft mode.
- None.
- CDPD-99371: Prometheus metrics do not function properly with KRaft mode
- 7.3.2
- If the Kafka cluster monitored by Streams Messaging Manager is running in KRaft mode and Streams Messaging Manager is configured to use Prometheus as its
metrics store, alerts related to the active controller do not work as
expected. In KRaft mode, the
broker_activecontrollercount
metric is reported by KRaft controllers rather than brokers. This change in
metric reporting can cause aggregation issues and lead to alerts triggering
indefinitely. Additionally, adding the
/api/prometheus-metrics endpoint from KRaft hosts
to the Prometheus configuration can cause anomalies in other alerts.
- Use Cloudera Manager as the
metrics store for KRaft-based Kafka clusters. Alternatively, if using
Prometheus, disable all alerts based on the
broker_activecontrollercount metric.
Known issues identified before Cloudera Runtime 7.3.2
Known issues identified before Cloudera Runtime 7.3.2 include only
unresolved issues from previous releases that continue to affect the Cloudera Runtime 7.3.2 base release.
- OPSAPS-59597: Streams Messaging Manager UI
logs are not supported by Cloudera Manager
- 7.1.7 and its SP
and CHF releases, 7.1.9 and its SP and CHF releases, 7.3.1 and its SP and
CHF releases, 7.3.2
- Cloudera Manager does not display a
Log Files menu for Streams Messaging Manager UI role (and Streams Messaging Manager UI logs cannot be displayed in the Cloudera Manager UI) because the logging type used by Streams Messaging Manager UI is not supported by Cloudera Manager.
- View the Streams Messaging Manager UI
logs on the host.
- CDPD-39313: Some numbers are not rendered properly in
Streams Messaging Manager UI
- 7.1.7 and its SP
and CHF releases, 7.1.9 and its SP and CHF releases, 7.3.1 and its SP and
CHF releases, 7.3.2
- Very large numbers can be imprecisely represented on
the UI. For example, bytes larger than 8 petabytes would lose
precision.
- None.
- OPSAPS-59553: Streams Messaging Manager
bootstrap server config should be updated based on Kafka's listeners
- 7.1.7 and its SP
and CHF releases, 7.1.9 and its SP and CHF releases, 7.3.1 and its SP and
CHF releases, 7.3.2
- Streams Messaging Manager does not show any
metrics for Kafka or Kafka Connect when multiple listeners are set in Kafka.
- Streams Messaging Manager cannot
identify multiple listeners and still points to bootstrap server using the
default broker port (9093 for SASL_SSL). You need to override bootstrap
server URL (hostname:port as set in the listeners for broker). Add the
bootstrap server details in Streams Messaging Manager safety valve
in the following path:
- In Cloudera Manager, go to
SMMConfigurationStreams
Messaging Manager Rest Admin Server Advanced Configuration
Snippet (Safety Valve) for
streams-messaging-manager.yaml.
- Add the following value for bootstrap
servers.
streams.messaging.manager.kafka.bootstrap.servers=<comma-separated list of brokers>
- Save your changes.
- Restart Streams Messaging Manager.
- CDPD-82560: Streams Messaging Manager known
unprotected endpoint
- 7.1.7 and its SP
and CHF releases, 7.1.9 and its SP and CHF releases, 7.3.1 and its SP and
CHF releases, 7.3.2
- The Streams Messaging Manager Frontend
exposes the
/cm-configs and /configs
public endpoints without requiring authentication. These endpoints do not
share any sensitive information.
- None.
