The workaround for https://issues.apache.org/jira/browse/KAFKA-6607# Says:
or use `consumer.position()` that takes the commit marker into account and would "step over it")
Note that this problem occurs with all consumers, not just Streams. We have implemented this solution in our project (as an option for those users concerned about the pseudo lag).
We have discovered that this technique will only work with
call does not include the marker "record".
- is related to
KAFKA-6607 Kafka Streams lag not zero when input topic transactional