[
https://issues.apache.org/jira/browse/FLINK-39128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emre Kartoglu updated FLINK-39128:
----------------------------------
Description:
After a job failover e.g. due to a transient error, the Dynamo DB source
connector keeps emiting the same millisBehindLatest metric. See attached
screenshot where millisBehindLatest was stuck at 141,673 ms. The metric got
reset when we updated the app with a new jar and the metric got unstuck.
was:
After a job failover e.g. due to a transient error, the Dynamo DB source
connector keeps emiting the same millisBehindLatest metric. See attached
screenshot where millisBehindLatest was stuck at 141,673
> DynamoDB CDC source connector millisBehindLatest metric gets stuck after
> failover
> ---------------------------------------------------------------------------------
>
> Key: FLINK-39128
> URL: https://issues.apache.org/jira/browse/FLINK-39128
> Project: Flink
> Issue Type: Bug
> Components: Connectors / DynamoDB
> Affects Versions: aws-connector-5.1.0
> Reporter: Emre Kartoglu
> Assignee: Emre Kartoglu
> Priority: Major
> Labels: AWS
> Attachments: Screenshot 2026-02-19 at 14.50.25.png
>
>
> After a job failover e.g. due to a transient error, the Dynamo DB source
> connector keeps emiting the same millisBehindLatest metric. See attached
> screenshot where millisBehindLatest was stuck at 141,673 ms. The metric got
> reset when we updated the app with a new jar and the metric got unstuck.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
