Question

我使用transaction.timeout.ms属性将生产者配置为10秒超时。但是，似乎事务在60秒后被中止，这要长得多。

请参阅以下程序：

Properties properties = new Properties();
properties.setProperty("bootstrap.servers", brokerConnectionString);
properties.setProperty("transactional.id", "my-transactional-id");
properties.setProperty("transaction.timeout.ms", "5000");

// start the first producer and write one event
KafkaProducer<String, String> producer =
        new KafkaProducer<>(properties, new StringSerializer(), new StringSerializer());
producer.initTransactions();
producer.beginTransaction();
producer.send(new ProducerRecord<>("topic", "value"));
// note the transaction is left non-completed

// start another producer with different txn.id and write second event
properties.setProperty("transactional.id", "another-transactional-id");
KafkaProducer<String, String> producer2 =
        new KafkaProducer<>(properties, new StringSerializer(), new StringSerializer());
producer2.initTransactions();
producer2.beginTransaction();
producer2.send(new ProducerRecord<>("topic", "value2"));
producer2.commitTransaction();

// consume the events using read-committed
Properties consumerProps = new Properties();
consumerProps.setProperty("bootstrap.servers", brokerConnectionString);
consumerProps.setProperty("group.id", "my-group");
consumerProps.setProperty("auto.offset.reset", "earliest");
consumerProps.setProperty("isolation.level", "read_committed");
KafkaConsumer<String, String> consumer = 
        new KafkaConsumer<>(consumerProps, new StringDeserializer(), new StringDeserializer());
consumer.subscribe(singleton("topic"));
while (true) {
    for (ConsumerRecord<String, String> record : consumer.poll(Duration.ofSeconds(1))) {
        logger.info(record.toString());
    }
}

value2将在约60秒后打印，这是transaction.timeout.ms参数的默认值。我对财产的理解不正确吗？

Answer 1

在编写问题的过程中，我找到了答案。代理配置为每60秒检查一次超时的生产者，因此事务在下一次检查时中止。此属性对其进行配置：transaction.abort.timed.out.transaction.cleanup.interval.ms。我在测试前就启动了经纪人，这就是为什么它总是要花大约60秒的时间。

卡夫卡忽略了生产者的`transaction.timeout.ms`

1 个答案: