[ 
https://issues.apache.org/jira/browse/FLINK-39599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-39599:
-----------------------------------
    Labels: pull-request-available  (was: )

> Expose pendingRecords metrics in FLINK Kinesis Connector
> --------------------------------------------------------
>
>                 Key: FLINK-39599
>                 URL: https://issues.apache.org/jira/browse/FLINK-39599
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: David
>            Priority: Major
>              Labels: pull-request-available
>
> The autoscaler (post-FLINK-31326) uses pendingRecords as optional input for 
> catch-up sizing. Kafka and Pulsar sources expose this; Kinesis does not, so 
> catch-up.duration is a no-op for Kinesis jobs.
> Proposal: Estimate pendingRecords as millisBehindLatest × 
> moving_avg_records_per_ms per split, summed across the operator. Document 
> explicitly that this is an estimate based on recent throughput, not an 
> authoritative count (the Kinesis API doesn't expose one).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to