[KAFKA-4689] OffsetValidationTest fails validation with "Current position greater than the total number of consumed records"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.10.2.1, 0.11.0.0
• Component/s: clients, consumer, system tests
• Labels: system-test-failure
• Assignee: Jason Gustafson
• Reporter: Ewen Cheslack-Postava
• Reviewer: Ewen Cheslack-Postava
• Created: 23/Jan/17 22:22
• Updated: 10/May/17 14:00
• Resolved: 30/Mar/17 22:52

Description

====================================================================================================
test_id: kafkatest.tests.client.consumer_test.OffsetValidationTest.test_consumer_bounce.clean_shutdown=False.bounce_mode=all
status: FAIL
run time: 1 minute 49.834 seconds

Current position greater than the total number of consumed records
Traceback (most recent call last):
File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py", line 123, in run
data = self.run_test()
File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py", line 176, in run_test
return self.test_context.function(self.test)
File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/mark/_mark.py", line 321, in wrapper
return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
File "/var/lib/jenkins/workspace/system-test-kafka/kafka/tests/kafkatest/tests/client/consumer_test.py", line 157, in test_consumer_bounce
"Current position greater than the total number of consumed records"
AssertionError: Current position greater than the total number of consumed records

See also https://issues.apache.org/jira/browse/KAFKA-3513?focusedCommentId=15791790&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15791790 which is another instance of this bug, which indicates the issue goes back at least as far as 1/17/2017. Note that I don't think we've seen this in 0.10.1 yet.

Issue Links

• links to: GitHub Pull Request #2771