Build failed in Jenkins: kafka-2.1-jdk8 #15

See Changes: [ismael] MINOR: AbstractIndex.close should unmap (#5757) -- [...truncated 437.02 KB...] kafka.admin.ReassignPartitionsCommandArgsTest >

Build failed in Jenkins: kafka-2.0-jdk8 #167

See Changes: [wangguoz] HOTFIX: Fix broken links (#5676) -- [...truncated 434.14 KB...] kafka.admin.ConfigCommandTest > shouldAddBrokerDynamicConfig STARTED

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

See

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

See

Build failed in Jenkins: kafka-2.0-jdk8 #166

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H33 (ubuntu xenial) in workspace

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

See Changes: [ismael] MINOR: Fix broken standalone ReplicationQuotasTestRig test (#5773) [github] MINOR: Fix remaining core, connect and clients tests to pass with Java

Build failed in Jenkins: kafka-trunk-jdk10 #618

See Changes: [github] KAFKA-4932: Update docs for KIP-206 (#5769) -- [...truncated 2.35 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Transitioning from Java 10 to Java 11 in Jenkins

Hi all, Java 11 was released recently and Java 10 is no longer supported. Java 11 is the first LTS release since the new Java release cadence was announced. As of today, all of our tests pass with Java 11 so it's time to transition Jenkins builds to use Java 11 instead of Java 10. I have updated

KAFKA-6654 custom SSLContext

KAFKA-6654 correctly states that there will never be enough configuration parameters to fully configure the SSLContext/SSLSocketFactory created by Kafka. For example, in our case, we need an alias to choose the key in the keystore, and we need an implementation of OCSP. KAFKA-6654 suggests to

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

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H32 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-380: Detect outdated control requests and bounced brokers using broker generation

Hey Stanislav, Sure. Thanks for your interest in this KIP. I am glad to provide more detail. broker A is initiating a controlled shutdown (restart). The Controller sends a StopReplicaRequest but it reaches broker A after it has started up again. He therefore stops replicating those partitions

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

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H32 (ubuntu xenial) in workspace

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

Thanks for your review, Joel and Dong. I've updated the KIP according to Dong's last comments. Cheers! Lucas On Tue, Oct 9, 2018 at 10:06 PM Dong Lin wrote: > Hey Lucas, > > Thanks for the KIP. Looks good overall. +1 > > I have two trivial comments which may be a bit useful to reader. > > -

[jira] [Created] (KAFKA-7496) KafkaAdminClient#describeAcls should handle invalid filters gracefully

Colin P. McCabe created KAFKA-7496: -- Summary: KafkaAdminClient#describeAcls should handle invalid filters gracefully Key: KAFKA-7496 URL: https://issues.apache.org/jira/browse/KAFKA-7496 Project:

[jira] [Created] (KAFKA-7495) AdminClient thread dies on invalid input

Xavier Léauté created KAFKA-7495: Summary: AdminClient thread dies on invalid input Key: KAFKA-7495 URL: https://issues.apache.org/jira/browse/KAFKA-7495 Project: Kafka Issue Type: Bug

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Hi John, Thanks for reviewing the KIP. > I didn't follow the addition of a new method to the QueryableStoreType > interface. Can you elaborate why this is necessary to support the new > exception types? To support the new exception types, I would check stream state in the following classes: -

[jira] [Resolved] (KAFKA-7307) Upgrade EasyMock for Java 11 support

[ https://issues.apache.org/jira/browse/KAFKA-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7307. Resolution: Not A Problem We migrated to mockito with full Java 11 support in the clients module

[jira] [Created] (KAFKA-7494) Update Jenkins jobs to use Java 11 instead of Java 10

Ismael Juma created KAFKA-7494: -- Summary: Update Jenkins jobs to use Java 11 instead of Java 10 Key: KAFKA-7494 URL: https://issues.apache.org/jira/browse/KAFKA-7494 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-378: Enable Dependency Injection for Kafka Streams handlers

Hi Wladimir, Of the two approaches in the KIP - i feel the second approach is cleaner. However, am i correct in assuming that you want to have the `ConfiguredStreamsFactory` as a ctor arg in `StreamsConfig` so that Spring can inject this for you? Otherwise you could just put the

[DISCUSS] KIP-381 Connect: Tell about records that had their offsets flushed in callback

Please help make the proposed changes in KIP-381 become reality. Please comment. KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-381%3A+Connect%3A+Tell+about+records+that+had+their+offsets+flushed+in+callback JIRA: https://issues.apache.org/jira/browse/KAFKA-5716 PR:

Re: [DISCUSS] KIP-380: Detect outdated control requests and bounced brokers using broker generation

Hi Patrick, Thanks for the KIP! Fixing such correctness issues is always very welcome - they're commonly hard to diagnose and debug when they happen in production. I was wondering if I understood the potential correctness issues correctly. Here is what I got: - If a broker bounces during

Re: [DISCUSS] KIP-380: Detect outdated control requests and bounced brokers using broker generation

Hey Patrick, Thanks much for the KIP. The KIP is very well written. LGTM. +1 (binding) Thanks, Dong On Tue, Oct 9, 2018 at 11:46 PM Patrick Huang wrote: > Hi All, > > Please find the below KIP which proposes the concept of broker generation > to resolve issues caused by controller missing