[
https://issues.apache.org/jira/browse/FLINK-26589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504964#comment-17504964
]
Danny Cranmer commented on FLINK-26589:
---------------------------------------
Merged to master
https://github.com/apache/flink/commit/69e5e4f7a7a7a534fe866f899e42e3e447233791
> Update the logging level of Kinesis Streams and Firehose sinks
> --------------------------------------------------------------
>
> Key: FLINK-26589
> URL: https://issues.apache.org/jira/browse/FLINK-26589
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Reporter: Zichen Liu
> Assignee: Ahmed Hamdy
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> h2. Motivation
> During the normal course of the KDS and KDF's sink's operation, we will
> likely encounter many failed persists to the destination due to throttling or
> otherwise. These are currently logged as warn. Also remove trace level
> logging in
> {code:java}
> submitRequestEntries{code}
> for these sinkWriters.
> *Proposed Solution*
> 1. We would like these messages to be logged as debug.
> 2. It would also be beneficial to adjust the wording to clarify that the
> entries will be requeued for retry.
> *Files to be changed*
> * KinesisStreamsSinkWriter
> ** when a request succeeds with a subset of the records and the remainder
> needs to be retried
> ** when the request has failed
> ** when submitRequestEntries is logging to trace
> * KinesisFirehoseSinkWriter
> ** when a request succeeds with a subset of the records and the remainder
> needs to be retried
> ** when the request has failed
> ** when submitRequestEntries is logging to trace
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
