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

See Changes: [wangguoz] KAFKA-8803: Remove timestamp check in completeTransitionTo (#8278) -- [...truncated 2.90 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-580: Exponential Backoff for Kafka Clients

Thanks for the explanation Boyang. One of the most common problems that we have in Kafka is with respect to metadata fetches. For example, if there is a broker failure, all clients start to fetch metadata at the same time and it often takes a while for the metadata to converge. In a high load

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

See Changes: [github] KAFKA-8803: Remove timestamp check in completeTransitionTo (#8278) -- [...truncated 2.92 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

See Changes: [github] KAFKA-8803: Remove timestamp check in completeTransitionTo (#8278) -- [...truncated 2.91 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

See Changes: [github] MINOR: double -Xss setting from 2m to 4m in build.gradle (#8264) -- [...truncated 5.91 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: [DISCUSS] KIP-580: Exponential Backoff for Kafka Clients

Thanks for the reply Sanjana. I guess I would like to rephrase my question 2 and 3 as my previous response is a little bit unactionable. My specific point is that exponential backoff is not a silver bullet and we should consider using it to solve known problems, instead of making the holistic

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

See Changes: [github] MINOR: double -Xss setting from 2m to 4m in build.gradle (#8264) -- [...truncated 2.90 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: Connect - Membership Protocol

Gentle reminder. + users. On Mon, Mar 16, 2020 at 11:27 PM mandeep gandhi wrote: > Hi, > > (PS - I did not use users list as this concerns some internals) > > I was trying to deploy the following config on a K8s cluster - > > Namespace - X1 Connect group id - G1Bootstrap servers - B1,

[jira] [Created] (KAFKA-9731) Increased fetch request rate with leader selector due to HW propagation

Vahid Hashemian created KAFKA-9731: -- Summary: Increased fetch request rate with leader selector due to HW propagation Key: KAFKA-9731 URL: https://issues.apache.org/jira/browse/KAFKA-9731 Project:

Re: Request Permission to Create Kafka Improvement Proposal

Hi, Zihan, Thanks for your interest. Just gave you the wiki permission (assuming it's lizihan). Jun On Mon, Mar 16, 2020 at 4:44 PM Zihan Li wrote: > Hi, > > I’m writing to request permission to create KIP. > > My proposal: > Currently there are two error handling options in Kafka connect,

Re: Request Permission to Create KIP

Hi, Cheng, Thanks for your interest. Just gave you the wiki permission. Jun On Tue, Mar 17, 2020 at 8:50 AM Cheng Pan <379377...@qq.com> wrote: > Hi all, > > > I’m writing to request permission to create KIP. > > > There is some discuss at https://issues.apache.org/jira/browse/KAFKA-8713. > >

Request Permission to Create KIP

Hi all, I??m writing to request permission to create KIP. There is some discuss at https://issues.apache.org/jira/browse/KAFKA-8713. I'd like to come up a KIP to push on it. Best regards Cheng Pan

[VOTE] 2.5.0 RC2

Hello Kafka users, developers and client-developers, This is the third candidate for release of Apache Kafka 2.5.0. * TLS 1.3 support (1.2 is now the default) * Co-groups for Kafka Streams * Incremental rebalance for Kafka Consumer * New metrics for better operational insight * Upgrade Zookeeper

[jira] [Reopened] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reopened KAFKA-3702: --- We changed the log level of the entry `Failed to send SSL Close message` from WARN to DEBUG,

Re: [kafka-clients] Re: [VOTE] 2.5.0 RC1

Thanks, Israel. I agree with Gwen, this is a great list and would be useful to add to our release candidate boilerplate. Since we found a blocker bug on RC1, I'll go ahead and close voting. RC2 will be announced shortly. -David On Tue, Mar 17, 2020 at 10:46 AM Israel Ekpo wrote: > Thanks for

Re: [kafka-clients] Re: [VOTE] 2.5.0 RC1

Thanks for the feedback, Gwen. I will create JIRA tasks to track the items shortly. The JIRA tasks will document the goals, expectations and relevant Kafka versions for each resource. I will volunteer for some of them and update the JIRA tasks accordingly. On Tue, Mar 17, 2020 at 12:51 AM Gwen

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

See Changes: [github] HOTFIX: StateDirectoryTest should use Set instead of List (#8305) [github] MINOR: cleanup and add tests to StateDirectoryTest (#8304) --

[jira] [Created] (KAFKA-9730) add tag "partition" to BrokerTopicMetrics so as to observe the metrics of partition in the same broker

Chia-Ping Tsai created KAFKA-9730: - Summary: add tag "partition" to BrokerTopicMetrics so as to observe the metrics of partition in the same broker Key: KAFKA-9730 URL:

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

See Changes: [github] HOTFIX: StateDirectoryTest should use Set instead of List (#8305) [github] MINOR: cleanup and add tests to StateDirectoryTest (#8304) --

[jira] [Created] (KAFKA-9729) Shrink inWriteLock time in SimpleAuthorizer

Jiao Zhang created KAFKA-9729: - Summary: Shrink inWriteLock time in SimpleAuthorizer Key: KAFKA-9729 URL: https://issues.apache.org/jira/browse/KAFKA-9729 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-6941) when passing port = 0 to worker, the advertisedPort still is 0 rather than a random port

[ https://issues.apache.org/jira/browse/KAFKA-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-6941. --- Resolution: Won't Fix > when passing port = 0 to worker, the advertisedPort still is 0

[jira] [Resolved] (KAFKA-6931) Make worker id configurable

[ https://issues.apache.org/jira/browse/KAFKA-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-6931. --- Resolution: Won't Fix > Make worker id configurable > --- > >

[jira] [Resolved] (KAFKA-7084) NewTopicBuilder#config should accept Map rather than Map

[ https://issues.apache.org/jira/browse/KAFKA-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-7084. --- Resolution: Won't Fix > NewTopicBuilder#config should accept Map rather than > Map >

Re: [Vote] KIP-569: Update DescribeConfigsResponse to include additional metadata information

Hi Shailesh, +1 (binding) Thanks for the KIP! Regards, Rajini On Tue, Mar 10, 2020 at 2:37 AM Gwen Shapira wrote: > +1 > Looks great. Thanks for the proposal, Shailesh. > > Gwen Shapira > Engineering Manager | Confluent > 650.450.2760 | @gwenshap > Follow us: Twitter | blog > > On Mon, Mar

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

See

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

See Changes: [github] MINOR: Fix build and JavaDoc warnings (#8291) -- [...truncated 2.91 MB...] org.apache.kafka.streams.test.ConsumerRecordFactoryTest >