There have been a few spurious failures in ReplicationTest.test_hard_bounce, where it was reported that a few of the acked messages were not consumed.
Checking the logs, however, it is clear that they were consumed, but ConsoleConsumerService failed to parse.
Lines causing parsing failure looks something like:
779725[2015-08-03 07:25:47,757] ERROR [ConsumerFetcherThread-console-consumer-78957_ip-172-31-5-20-1438586715191-249db71c-0-1], Error for partition [test_topic,0] to broker 1:class kafka.common.NotLeaderForPartitionException (kafka.consumer.ConsumerFetcherThread)
(i.e. the consumed message, and a log message appear on the same line)
ConsoleConsumerService simply tries to strip each line of whitespace and parse as an integer, which will clearly fail in this case.
Solution should either redirect stderr elsewhere or update parsing to handle this.
There have been a few spurious failures in ReplicationTest.test_hard_bounce, where it was reported that a few of the acked messages were not consumed.
Checking the logs, however, it is clear that they were consumed, but ConsoleConsumerService failed to parse.
Lines causing parsing failure looks something like:
779725[2015-08-03 07:25:47,757] ERROR [ConsumerFetcherThread-console-consumer-78957_ip-172-31-5-20-1438586715191-249db71c-0-1], Error for partition [test_topic,0] to broker 1:class kafka.common.NotLeaderForPartitionException (kafka.consumer.ConsumerFetcherThread)
(i.e. the consumed message, and a log message appear on the same line)
ConsoleConsumerService simply tries to strip each line of whitespace and parse as an integer, which will clearly fail in this case.
Solution should either redirect stderr elsewhere or update parsing to handle this.