You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolves#1587
See javadoc for `ConsumerProperties.setFixTxOffsets()` for more information.
**cherry-pick to 2.5.x**
* Add `this.` to `logger` to honor Checkstyle
Copy file name to clipboardExpand all lines: src/reference/asciidoc/kafka.adoc
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2235,6 +2235,13 @@ The default executor creates threads named `<name>-C-n`; with the `KafkaMessageL
2235
2235
|`ALPHA`
2236
2236
|Exactly Once Semantics mode; see <<exactly-once>>.
2237
2237
2238
+
|fixTxOffsets
2239
+
|`false`
2240
+
|When consuming records produced by a transactional producer, and the consumer is positioned at the end of a partition, the lag can incorrectly be reported as greater than zero, due to the pseudo record used to indicate transaction commit/rollback and, possibly, the presence of rolled-back records.
2241
+
This does not functionally affect the consumer but some users have expressed concern that the "lag" is non-zero.
2242
+
Set this property to `true` and the container will correct such mis-reported offsets.
2243
+
The check is performed before the next poll to avoid adding significant complexity to the commit processing.
2244
+
2238
2245
|groupId
2239
2246
|`null`
2240
2247
|Overrides the consumer `group.id` property; automatically set by the `@KafkaListener` `id` or `groupId` property.
0 commit comments