[ https://issues.apache.org/jira/browse/KAFKA-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ray Chiang updated KAFKA-5035: ------------------------------ Component/s: system tests > throttling_test fails due to parsing exception in console consumer > ------------------------------------------------------------------ > > Key: KAFKA-5035 > URL: https://issues.apache.org/jira/browse/KAFKA-5035 > Project: Kafka > Issue Type: Bug > Components: system tests > Reporter: Jun Rao > Priority: Major > > The system test sometimes fails due to > [INFO - 2017-04-06 09:38:58,950 - kafka - bootstrap_servers - lineno:549]: > Bootstrap client port is: 9092 > [INFO - 2017-04-06 09:39:01,584 - background_thread - _protected_worker - > lineno:38]: BackgroundThreadService threw exception: > [INFO - 2017-04-06 09:39:01,585 - background_thread - _protected_worker - > lineno:39]: Traceback (most recent call last): > File > "/var/lib/jenkins/workspace/system-tests-kafka-kip-101/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/services/background_thread.py", > line 35, in _protected_worker > self._worker(idx, node) > File > "/var/lib/jenkins/workspace/system-tests-kafka-kip-101/kafka/tests/kafkatest/services/console_consumer.py", > line 269, in _worker > msg = self.message_validator(msg) > File > "/var/lib/jenkins/workspace/system-tests-kafka-kip-101/kafka/tests/kafkatest/utils/util.py", > line 53, in is_int > raise Exception("Unexpected message format (expected an integer). > Message: %s" % (msg)) > Exception: Unexpected message format (expected an integer). Message: > SSXVNJHPDQDXVCRASTVYBCWVMGNYKRXVZXKGXTSPSJDGYLUEGQFLAQLOCFLJBEPOWFNSOMYARHAOPUFOJHHDXEHXJBHWGSMZJGNLONJVXZXZOZITKXJBOZWDJMCBOSYQQKCPRRDCZWMRLFXBLGQPRPGRNTAQOOSVXPKJPJLAVSQCCRXFRROLL > The issue seems to be the following. > 1. The test first runs ProducerPerformance with some binary data. > 2. It then starts VerifiableProducer and console consumer for verifying. > Console consumer in step 2 reads from the latest offset with the intend to > avoid reading any binary data published in step 1. However, > ProducerPerformance doesn't use acks=all, which may break this assumption in > some corner cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)