Build failed in Jenkins: kafka-trunk-jdk8 #4745

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10306: GlobalThread should fail on InvalidOffsetException (#9075) -- [...truncated 2.76 MB...]

[jira] [Created] (KAFKA-10312) MetadataCache.getPartitionMetadata may return incorrect error code when partition's leader is not present at the MetadataCache

2020-07-26 Thread Raman Verma (Jira)
Raman Verma created KAFKA-10312: --- Summary: MetadataCache.getPartitionMetadata may return incorrect error code when partition's leader is not present at the MetadataCache Key: KAFKA-10312 URL:

Re: [DISCUSS] KIP-595: A Raft Protocol for the Metadata Quorum

2020-07-26 Thread Unmesh Joshi
>>Could you clarify on this question? Which part of the raft group doesn't >>know about leader dis-connection? The leader of the controller quorum is partitioned from the controller cluster, and a different leader is elected for the remaining controller cluster. I think there are two things here,

Build failed in Jenkins: kafka-trunk-jdk14 #320

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10306: GlobalThread should fail on InvalidOffsetException (#9075) [github] MINOR: Recommend Java 11 (#9080) -- [...truncated 2.80 MB...]

[jira] [Created] (KAFKA-10311) Flaky test KafkaAdminClientTest#testMetadataRetries

2020-07-26 Thread Boyang Chen (Jira)
Boyang Chen created KAFKA-10311: --- Summary: Flaky test KafkaAdminClientTest#testMetadataRetries Key: KAFKA-10311 URL: https://issues.apache.org/jira/browse/KAFKA-10311 Project: Kafka Issue

Build failed in Jenkins: kafka-trunk-jdk11 #1671

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] MINOR: INFO log4j when request re-join (#9068) -- [...truncated 3.20 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-2.6-jdk8 #98

2020-07-26 Thread Apache Jenkins Server
See Changes: [matthias] KAFKA-10306: GlobalThread should fail on InvalidOffsetException (#9075) -- [...truncated 3.15 MB...]

Re: [DISCUSS] KIP-595: A Raft Protocol for the Metadata Quorum

2020-07-26 Thread Boyang Chen
Thanks for the questions Unmesh! On Sun, Jul 26, 2020 at 6:18 AM Unmesh Joshi wrote: > Hi, > > In the FetchRequest Handling, how to make sure we handle scenarios where > the leader might have been disconnected from the cluster, but doesn't know > yet? > Could you clarify on this question? Which

[DISCUSS] KIP-630: Kafka Raft Snapshot

2020-07-26 Thread Jose Garcia Sancio
Hi All, I would like to start a discussion on KIP-630: https://cwiki.apache.org/confluence/x/exV4CQ This proposal specifies extensions to KIP-595 to support generating snapshots for the replicated log. Please let me know if you have any comments and suggestions. Thanks! -- -Jose

[jira] [Created] (KAFKA-10310) Kafka Raft Snapshot

2020-07-26 Thread Jose Armando Garcia Sancio (Jira)
Jose Armando Garcia Sancio created KAFKA-10310: -- Summary: Kafka Raft Snapshot Key: KAFKA-10310 URL: https://issues.apache.org/jira/browse/KAFKA-10310 Project: Kafka Issue Type:

Build failed in Jenkins: kafka-trunk-jdk11 #1670

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10306: GlobalThread should fail on InvalidOffsetException (#9075) [github] MINOR: Recommend Java 11 (#9080) -- [...truncated 3.21 MB...]

Re: [DISCUSS] KIP-622 Add currentSystemTimeMs and currentStreamTimeMs to ProcessorContext

2020-07-26 Thread Matthias J. Sax
Hi, I just had one more thought about an additional improvement we might want to include in this KIP. Kafka Streams ships with a `WallclockTimestampExtractor` that just returns `System.currentTimeMillis()` and thus, cannot be mocked. And it seems that there is no way for a user to build a custom

Re: [DISCUSS] KIP-645: Replace abstract class Windows with a proper interface

2020-07-26 Thread John Roesler
Thanks Sophie and Boyang for asking for specifics. As far as I can tell, if we were to _remove_ all the non-public-method members from Windows, including any constructors, we are left with effectively an interface. I think this was my plan before. I don't think I realized at the time that it's

Jenkins build is back to normal : kafka-trunk-jdk11 #1669

2020-07-26 Thread Apache Jenkins Server
See

Build failed in Jenkins: kafka-2.5-jdk8 #171

2020-07-26 Thread Apache Jenkins Server
See Changes: [ismael] KAFKA-10158: Fix flaky -- [...truncated 2.93 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Build failed in Jenkins: kafka-trunk-jdk14 #319

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10158: Fix flaky -- [...truncated 6.41 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Build failed in Jenkins: kafka-trunk-jdk8 #4744

2020-07-26 Thread Apache Jenkins Server
See Changes: [github] KAFKA-10158: Fix flaky -- [...truncated 3.18 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Created] (KAFKA-10309) KafkaProducer's sendOffsetsToTransaction should not block infinitively

2020-07-26 Thread Sasaki Toru (Jira)
Sasaki Toru created KAFKA-10309: --- Summary: KafkaProducer's sendOffsetsToTransaction should not block infinitively Key: KAFKA-10309 URL: https://issues.apache.org/jira/browse/KAFKA-10309 Project: Kafka

Re: [VOTE] KIP-622 Add currentSystemTimeMs and currentStreamTimeMs to ProcessorContext

2020-07-26 Thread John Roesler
Thanks William, I’m +1 (binding) Thanks, John On Fri, Jul 24, 2020, at 20:22, Sophie Blee-Goldman wrote: > Thanks all, +1 (non-binding) > > Cheers, > Sophie > > On Wed, Jul 8, 2020 at 4:02 AM Bruno Cadonna wrote: > > > Thanks Will and Piotr, > > > > +1 (non-binding) > > > > Best, > > Bruno

Re: [DISCUSS] KIP-406: GlobalStreamThread should honor custom reset policy

2020-07-26 Thread Navinder Brar
Hi, Sorry, it took some time to respond back. “but I thought we would pass the config through to the client.” >> @John, sure we can use the config in GloablStreamThread, that could be one >> of the way to solve it. @Matthias, sure cleaning the store and recreating is one way but

Re: [DISCUSS] KIP-595: A Raft Protocol for the Metadata Quorum

2020-07-26 Thread Unmesh Joshi
Hi, In the FetchRequest Handling, how to make sure we handle scenarios where the leader might have been disconnected from the cluster, but doesn't know yet? As discussed in the Raft Thesis section 6.4, the linearizable semantics of read requests is implemented in LogCabin by sending heartbeat to