Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #308

See Changes: [github] KAFKA-10832: Fix Log to use the correct ProducerStateManager instance when updating producers (#9718) -- [...truncated 6.99 MB...] or

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #329

See

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #282

See

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi, Colin, Thanks for the reply. Just a couple of more comments below. 210. Since we are deprecating zookeeper.connection.timeout.ms, should we add a new config to bound the time for a broker to connect to the controller during starting up? 211. BrokerHeartbeat no longer has the state field in t

[jira] [Resolved] (KAFKA-10832) Recovery logic is using incorrect ProducerStateManager instance when updating producers

[ https://issues.apache.org/jira/browse/KAFKA-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10832. - Fix Version/s: 2.8.0 Resolution: Fixed Merged the PR to trunk. > Recovery logic is using incorre

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Thanks, Guozhang! All of your feedback sounds good to me. I’ll update the KIP when I am able. 3) I believe it is the position after the fetch, but I will confirm. I think omitting position may render beginning and end offsets useless as well, which leaves only lag. That would be fine with me, b

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Hello John, Thanks for the updates! I've made a pass on the KIP and also the POC PR, here are some minor comments: 1) nit: "receivedTimestamp" -> it seems the metadata keep getting updated, and we do not create a new object but just update the values in-place, so maybe calling it `lastUpdateTimst

[jira] [Created] (KAFKA-10848) Allow fine grained control over cross-partition processing order

Matthias J. Sax created KAFKA-10848: --- Summary: Allow fine grained control over cross-partition processing order Key: KAFKA-10848 URL: https://issues.apache.org/jira/browse/KAFKA-10848 Project: Kafka

[VOTE] voting on KIP-631: the quorum-based Kafka controller

Hi all, I'd like to restart the vote on KIP-631: the quorum-based Kafka Controller. The KIP is here: https://cwiki.apache.org/confluence/x/4RV4CQ The original DISCUSS thread is here: https://lists.apache.org/thread.html/r1ed098a88c489780016d963b065e8cb450a9080a4736457cd25f323c%40%3Cdev.kafka.

[jira] [Created] (KAFKA-10847) Avoid spurious left/outer join results in stream-stream join

Matthias J. Sax created KAFKA-10847: --- Summary: Avoid spurious left/outer join results in stream-stream join Key: KAFKA-10847 URL: https://issues.apache.org/jira/browse/KAFKA-10847 Project: Kafka

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

On Wed, Dec 9, 2020, at 10:10, Jun Rao wrote: > Hi, Colin, > > Thanks for the update. A few more follow up comments. > Hi Jun, Thanks again for the review. > 100. FailedReplicaRecord: Since this is reported by each broker > independently, perhaps we could use a more concise representation that

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Thanks for the KIP! +1 (non-binding) walker On Wed, Dec 9, 2020 at 11:40 AM Bruno Cadonna wrote: > Thanks for the KIP, John! > > +1 (non-binding) > > Best, > Bruno > > On 08.12.20 18:03, John Roesler wrote: > > Hello all, > > > > There hasn't been much discussion on KIP-695 so far, so I'd > >

[VOTE] 2.6.1 RC3

Hello Kafka users, developers and client-developers, This is the fourth candidate for release of Apache Kafka 2.6.1. Since RC2, the following JIRAs have been fixed: KAFKA-10811, KAFKA-10802 Release notes for the 2.6.1 release: https://home.apache.org/~mimaison/kafka-2.6.1-rc3/RELEASE_NOTES.html

[jira] [Created] (KAFKA-10846) FileStreamSourceTask buffer can grow without bound

Tom Bentley created KAFKA-10846: --- Summary: FileStreamSourceTask buffer can grow without bound Key: KAFKA-10846 URL: https://issues.apache.org/jira/browse/KAFKA-10846 Project: Kafka Issue Type:

Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #62

See

Re: [DISCUSS] KIP-698: Add Explicit User Initialization of Broker-side State to Kafka Streams

Thanks Bruno, It’s your decision. I was thinking that it’s appropriate to mention such discussed and rejected/deferred items under “Rejected Alternatives” so that future generations will know whether we even thought of it and why we didn’t do it right now. Thanks, John On Fri, Dec 11, 2020, a

[jira] [Created] (KAFKA-10845) Introduce a `VisibleForTesting` annotation

dengziming created KAFKA-10845: -- Summary: Introduce a `VisibleForTesting` annotation Key: KAFKA-10845 URL: https://issues.apache.org/jira/browse/KAFKA-10845 Project: Kafka Issue Type: Improvemen

Re: [VOTE] 2.7.0 RC5

Updated with link to successful Jenkins build. * Successful Jenkins builds for the 2.7 branch: Unit/integration tests: https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-2.7-jdk8/detail/kafka-2.7-jdk8/78/ On Thu, Dec 10, 2020 at 5:17 PM Bill Bejeck wrote: > Hello Kafka u

Jenkins build is back to normal : Kafka » kafka-2.7-jdk8 #78

See

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #61

See Changes: -- [...truncated 3.16 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldNotUpdateStoreForSmallerValue[Eos enabled = false] PASSED org.apache.kafka.

[jira] [Created] (KAFKA-10844) groupBy without shuffling

Mathieu DESPRIEE created KAFKA-10844: Summary: groupBy without shuffling Key: KAFKA-10844 URL: https://issues.apache.org/jira/browse/KAFKA-10844 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-10843) Kafka Streams metadataForKey method returns null but allMetadata has the details

Maria Thomas created KAFKA-10843: Summary: Kafka Streams metadataForKey method returns null but allMetadata has the details Key: KAFKA-10843 URL: https://issues.apache.org/jira/browse/KAFKA-10843 Proj

Re: [DISCUSS] KIP-698: Add Explicit User Initialization of Broker-side State to Kafka Streams

Thanks Sophie for the feedback! I agree with you on not logging a warning for a decision, we haven't taken and on logging a warning for possible data loss with automatic initialization. I would say this is a implementation detail that we can further discuss on the PR. Regarding the parameter

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #328

See Changes: [github] MINOR: Update jmh to 1.27 for async profiler support (#9129) -- [...truncated 3.49 MB...] org.apache.kafka.streams.test.OutputVerifierT