You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gabor Somogyi (JIRA)" <ji...@apache.org> on 2019/02/20 08:40:00 UTC
[jira] [Updated] (KAFKA-7927) Old command line tools should notify
user when unsupported isolation-level parameter provided
[ https://issues.apache.org/jira/browse/KAFKA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Somogyi updated KAFKA-7927:
---------------------------------
Summary: Old command line tools should notify user when unsupported isolation-level parameter provided (was: Read committed receives aborted events)
> Old command line tools should notify user when unsupported isolation-level parameter provided
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-7927
> URL: https://issues.apache.org/jira/browse/KAFKA-7927
> Project: Kafka
> Issue Type: Bug
> Components: consumer, core, producer
> Affects Versions: 1.0.0
> Reporter: Gabor Somogyi
> Priority: Blocker
> Attachments: KafkaProducer.scala, consumer.log, producer.log.gz
>
>
> When a kafka client produces ~30k events and at the end it aborts the transaction a consumer can read part of the aborted messages when "isolation.level" set to "READ_COMMITTED".
> Kafka client version: 2.0.0
> Kafka broker version: 1.0.0
> Producer:
> {code:java}
> java -jar kafka-producer/target/kafka-producer-0.0.1-SNAPSHOT-jar-with-dependencies.jar gsomogyi-cdh5144-220cloudera2-1.gce.cloudera.com:9092 src-topic
> {code}
> See attached code.
> Consumer:
> {code:java}
> kafka-console-consumer --zookeeper localhost:2181 --topic src-topic --from-beginning --isolation-level read_committed
> {code}
> Same behavior seen when re-implemented the consumer in scala.
> The whole application can be found here: https://github.com/gaborgsomogyi/kafka-semantics-tester
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)