Viliam Durina created KAFKA-6099:
------------------------------------
Summary: Seeking consumer to evicted offset resets the offset
Key: KAFKA-6099
URL: https://issues.apache.org/jira/browse/KAFKA-6099
Project: Kafka
Issue Type: Bug
Components: consumer
Affects Versions: 0.11.0.1
Environment: Windows
Reporter: Viliam Durina
We use manual partition assignment and save the offsets to our storage. The
topic also has short "retention.ms" property. When we try to restart
consumption from an already evicted offset, the offset is reset according to
the "auto.offset.reset" property. That is:
- if "latest" is configured, it only returns records that were inserted after
the `seek` call
- if "earliest" is configured, it tries to restart at 0, which fails for the
same reason, because offset=0 is also evicted.
Expected behavior is to report the situation with an exception, thrown from
either `seek()` or `poll()` call. The user will then be expected to
`seekToBeginning` or `seekToEnd` or to any other position.
Another option is to restart at earliest available record, regardless of the
value of the "auto.offset.reset" property. However, this way the consumer has
no way of knowing that it missed some records it expected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
