Member since
11-23-2021
3
Posts
0
Kudos Received
0
Solutions
12-06-2021
09:50 PM
@jaeseung, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
11-24-2021
12:11 PM
Hi @jaeseung For SMM "WARNING": The status of a replication flow is calculated based on the replication latency and the throughput. if any of the metrics are not present -> INACTIVE if latency max and latency age is smaller than a fixed grace period (60 sec), and throughput max is not zero -> ACTIVE if throughput age is smaller than a fixed grace period (60 sec), and throughput max is not zero -> WARNING otherwise -> INACTIVE
... View more
11-24-2021
12:05 PM
Hi @jaeseung The client configurations have to be passed using the cluster alias replication: for consumer configs: primary->secondary.consumer.<config> > for producer configs: primary->secondary.producer.override.<config> Please try using Under SRM configs: <source>-><target>.producer.override.max.request.size=<desired value> If that doesn't work use: <source>-><target>.producer.max.request.size=<desired value>
... View more