SpringCloud/spring-cloud-stream
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Supporting DLQ in batch mode (#2649)

Browse Source 
* Supporting DLQ in batch mode

Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2317

* PR review

Co-authored-by: Gary Russell <grussell@vmware.com>

---------

Co-authored-by: Gary Russell <grussell@vmware.com>
This commit is contained in:
Soby Chacko
2023-02-13 12:05:28 -05:00
committed by GitHub
parent 756f02d435
commit 371815806b
3 changed files with 212 additions and 136 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/src/main/asciidoc/kafka/kafka_overview.adoc
View File

@@ -384,6 +384,9 @@ Starting with version 3.0, when `spring.cloud.stream.binding.<name>.consumer.bat
Otherwise, the method will be called with one record at a time.
The size of the batch is controlled by Kafka consumer properties `max.poll.records`, `fetch.min.bytes`, `fetch.max.wait.ms`; refer to the Kafka documentation for more information.
Starting with version `4.0.2`, the binder supports DLQ capabilities when consuming in batch mode.
Keep in mind that, when using DLQ on a consumer binding that is in batch mode, all the records received from the previous poll will be delivered to the DLQ topic.
IMPORTANT: Retry within the binder is not supported when using batch mode, so `maxAttempts` will be overridden to 1.
You can configure a `DefaultErrorHandler` (using a `ListenerContainerCustomizer`) to achieve similar functionality to retry in the binder.
You can also use a manual `AckMode` and call `Ackowledgment.nack(index, sleep)` to commit the offsets for a partial batch and have the remaining records redelivered.