What's New in Streams Replication Manager
Learn about the new features of Streams Replication Manager in Cloudera Runtime 7.2.11.
The SRM Service role tries to recover automatically if errors are encountered
The SRM Service role might encounter errors that make metrics processing impossible. An example of this is when the target Kafka cluster is not reachable. If such an error is encountered, the SRM Service role now tries to recover automatically. If recovery is successful, the SRM Service role continues to monitor replications and displays as healthy in Cloudera Manager. However, during recovery, until the recovery is successful, the role displays as unhealthy.
New health tests for the SRM Service role
New health tests are introduced for the SRM Service role. These health tests describe the state of the SRM Service role. If the SRM Service role encounters an error that makes metrics processing impossible, Cloudera Manager now correctly displays the SRM Service role as unhealthy.
The wait time before starting new connectors is now configurable
connect.start.task.timeout.ms, is added. This property controls the timeout of the tasks executed when starting connectors. The default value of the property is 20000 ms. You can configure the property on a replication level through the Streams Replication Manager's Replication Configs Cloudera Manager property. For example:
Custom lists of supported/excluded cipher suites and TLS/SSL protocols are configurable for the SRM Service role
- Supported SSL/TLS Cipher
- Excluded SSL/TLS Cipher
- Supported SSL/TLS
- Excluded SSL/TLS