Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Auto Closed
-
0.7
-
None
-
None
Description
When calling ConsumerConnector.createMessageStreams in rapid succession, the Consumer offset is incorrectly advanced causing the consumer to lose messages. This seems to happen when createMessageStreams is called before the rebalancing triggered by the previous call to createMessageStreams has completed.
Annotated log messages from two different test runs. For each test run, 20k messages were written to "mytopic" and "mytopic1" each with no consumers running. Once the messages had all been sent, the consumers were started up