[jira] [Created] (KAFKA-6635) Producer close does not await pending transaction

Jason Gustafson created KAFKA-6635: -- Summary: Producer close does not await pending transaction Key: KAFKA-6635 URL: https://issues.apache.org/jira/browse/KAFKA-6635 Project: Kafka Issue Typ

Streams meetup@LinkedIn (Mar 21)

Hi Kafka users and developers, We are going to host our quarterly Stream Processing Meetup@LinkedIn on Mar 21. There will be three talks about Apache Pulsar, Apache Calcite and Apache Samza, as well as LinkedIn's latest K-V store Venice built on top of Apache Kafka and Apache Samza. Please check

Jenkins build is back to normal : kafka-trunk-jdk8 #2464

See

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Dong, I was thinking a bit about log compaction after a partition split. I think the best you could hope for in terms of efficiency is that the network overhead would be proportional to the number of remapped keys that need cleaning. One thought I had which gets close to this is to propagate a

Jenkins build is back to normal : kafka-trunk-jdk7 #3241

See

Build failed in Jenkins: kafka-trunk-jdk9 #462

See Changes: [github] MINOR: Reduce ZK reads and ensure ZK watch is set for listener update -- [...truncated 1.48 MB...] kafka.message.ByteBufferMessageSetTest > testWrite

Build failed in Jenkins: kafka-1.1-jdk7 #73

See Changes: [rajinisivaram] MINOR: Reduce ZK reads and ensure ZK watch is set for listener update -- [...truncated 415.94 KB...] kafka.tools.ConsoleConsumerTest > shouldPars

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi Jun, thanks for your mail. Thank you for your questions! I think they are really good and tackle the core of the problem I see. I will answer inline, mostly but still want to set the tone here. The core strength of kafka is what Martin once called the kappa-Architecture. How does this work?