What's New in Streams Replication Manager
Learn about the new features of Streams Replication Manager in Cloudera Runtime 7.1.7.
Sensitive cluster connection information is now stored securely
SRM is now capable of storing all sensitive data in a secure manner. As a result of this
improvement, the recommended method of how you configure clusters and cluster connection
information for the SRM service (Driver and Service roles) and the
srm-control tool has changed.
Previously, cluster connection information (aliases, bootstrap servers, security properties) was configured through the Streams Replication Manager's Replication Configs Cloudera Manager property. From now on, both external and co-located clusters can be defined using a new configuration pane in Cloudera Manager. In addition, co-located clusters can also be configured with a service dependency. The new configuration pane is called Kafka credentials and can be found in .
Additionally, an intermediary keystore that stores connection related sensitive data called
SRM client's secure storage can be set up and configured in Cloudera Manager. This secure
storage acts as an extension to the
srm-control tool’s default
configuration and must be set up for the tool if SRM is replicating a secure cluster.
Using the new configuration options and methods makes it possible to securely store all sensitive data that is added to SRM’s configuration.
New documentation is introduced that walks users through the new configuration workflows.
For more information, on how to configure clusters using the new configuration options and
workflow, see Defining and adding clusters for replication. For
more information regarding the new configuration workflow for the
srm-control tool, see Configuring srm-control. Additionally, all existing
documentation affected by this change is also updated.
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