Closed colinking closed 4 years ago
Actually, upon debugging further, it seems that DynamoDBMasterToReplicasPipeline
calls the deprecated DynamoDBReplicationEmitter
constructor which takes only the streams configuration. Therefore, it isn't actually using the NoopCloudWatch
instance, but instead creates a new Cloudwatch client.
emitCloudWatchMetrics
inDynamoDBReplicationEmitter.java
callsputMetricDataAsync
on the cloudwatch object, which is an instance ofNoopCloudWatch
when--dontPublishCloudwatch
is specified. This leads to unintended behavior, and metric publishing failures.