Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #287

See Changes: [github] Revert "MINOR: fix typo in `AbstractIndex.scala` (#9745)" (#9751) -- [...truncated 6.93 MB...]

Re: [DISCUSS] KIP-693: Client-side Circuit Breaker for Partition Write Errors

Hello George, Thanks for the KIP. Just a few questions to help us understanding the design details: 1) Why does the default implementation have a criterion of when it is enabled -- i.e. after a certain number of messages have been successfully sent -- instead of always enabled? Also how would

Re: [DISCUSS] KIP-694: Support Reducing Partitions for Topics

Hello George, Thanks for submitting this KIP. On the high-level I think I agree that handling keyed messages is a very complicated issue and maybe we can just start with the easy scenario that does not involve them. Pushing the burden to admin users to determine if it is really safe to delete

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

See

[jira] [Created] (KAFKA-10855) Non-local return in envelope validation in causes unexpected response send

Jason Gustafson created KAFKA-10855: --- Summary: Non-local return in envelope validation in causes unexpected response send Key: KAFKA-10855 URL: https://issues.apache.org/jira/browse/KAFKA-10855

[jira] [Created] (KAFKA-10856) Convert sticky assignor userData schemas to use generated protocol

dengziming created KAFKA-10856: -- Summary: Convert sticky assignor userData schemas to use generated protocol Key: KAFKA-10856 URL: https://issues.apache.org/jira/browse/KAFKA-10856 Project: Kafka

[jira] [Created] (KAFKA-10854) Fix flaky kafka.network.SocketServerTest.testConnectionRatePerIp test

Luke Chen created KAFKA-10854: - Summary: Fix flaky kafka.network.SocketServerTest.testConnectionRatePerIp test Key: KAFKA-10854 URL: https://issues.apache.org/jira/browse/KAFKA-10854 Project: Kafka

Kafka support Arm CI

Hi Kafka: Recently we met a problem that we have to test and run Kafka on ARM arch. While searching the Kafka community, I didn’t find an official ARM release version. Since Kafka is made by Java and Scala language which can be run cross-platform usually, I think Kafka can be built and run

Re: [DISCUSS] KIP-693: Client-side Circuit Breaker for Partition Write Errors

Hi Jun and Justin, Many thanks for taking a look at our proposal and for the pointer! We learned about the mechanism proposed to enhance StickyPartitioner. Both methods aim to exclude brokers with transient errors and prevent cluster wide failure. The difference lies in the criteria used to

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

On Fri, Dec 11, 2020, at 17:07, Jun Rao wrote: > 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

Re: [DISCUSS] KIP-687: Automatic Reloading of Security Store

Hey there, bumping up this thread to see if there are further questions regarding the updated proposal. Best, Boyang On Thu, Dec 10, 2020 at 11:52 AM Boyang Chen wrote: > After some offline discussions, we believe that it's the right direction > to go by doing a hybrid approach which includes

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

Hello Bruno, Just a few more questions about the KIP: 1) If the internal topics exist but the calculated num.partitions do not match the existing topics, what would Streams do; 2) Since `init()` is a blocking call (we only return after all topics are confirmed to be created), should we have a

[jira] [Created] (KAFKA-10853) Replication protocol deficiencies with workloads requiring high durability guarantees

Kyle Ambroff-Kao created KAFKA-10853: Summary: Replication protocol deficiencies with workloads requiring high durability guarantees Key: KAFKA-10853 URL: https://issues.apache.org/jira/browse/KAFKA-10853

[GitHub] [kafka-site] scott-confluent opened a new pull request #314: [minor] Adding many more companies to powered by page

scott-confluent opened a new pull request #314: URL: https://github.com/apache/kafka-site/pull/314 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

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

Thanks, Bruno! I'm +1 (binding) -John On Mon, 2020-12-14 at 09:57 -0600, Leah Thomas wrote: > Thanks for the KIP Bruno, LGTM. +1 (non-binding) > > Cheers, > Leah > > On Mon, Dec 14, 2020 at 4:29 AM Bruno Cadonna wrote: > > > Hi, > > > > I'd like to start the voting on KIP-698 that proposes

Re:[DISCUSS] KIP-700: Add Describe Cluster API

> I'd like to propose a small KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-700%3A+Add+Describe+Cluste r+API Hi David, Since this is a new API, would it be possible to include each broker's JMX port in the response? That's currently not part of the metadata API and it would have

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi Jun, Thanks for your comments. Please go through the inline replies. 5102.2: It seems that both positions can just be int. Another option is to have two methods. Would it be clearer? InputStream fetchLogSegmentData(RemoteLogSegmentMetadata remoteLogSegmentMetadata, int startPosition)

Re: [VOTE] KIP-696: Update Streams FSM to clarify ERROR state meaning

Thank you everyone, KIP-696 has passed with 3 binding votes (Guozhang, John and Sophie) and 2 non-binding votes (Leah and Bruno) walker On Thu, Dec 10, 2020 at 11:00 AM Sophie Blee-Goldman wrote: > KIP looks good to me, thanks Walker! > > +1 (binding) > > -Sophie > > On Thu, Dec 10, 2020 at

[DISCUSS] KIP-700: Add Describe Cluster API

Hi all, I'd like to propose a small KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-700%3A+Add+Describe+Cluster+API Please let me know what you think. Best, David

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

Thanks for the KIP Bruno, LGTM. +1 (non-binding) Cheers, Leah On Mon, Dec 14, 2020 at 4:29 AM Bruno Cadonna wrote: > Hi, > > I'd like to start the voting on KIP-698 that proposes an explicit user > initialization of broker-side state for Kafka Streams instead of letting > Kafka Streams setting

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

See

[jira] [Created] (KAFKA-10852) AlterIsr should be a cluster action

Ismael Juma created KAFKA-10852: --- Summary: AlterIsr should be a cluster action Key: KAFKA-10852 URL: https://issues.apache.org/jira/browse/KAFKA-10852 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-10851) Add Cluster Describe API

David Jacot created KAFKA-10851: --- Summary: Add Cluster Describe API Key: KAFKA-10851 URL: https://issues.apache.org/jira/browse/KAFKA-10851 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-10850) Use 'Int.box' to replace deprecated 'new Integer' from BrokerToControllerRequestThreadTest

Chia-Ping Tsai created KAFKA-10850: -- Summary: Use 'Int.box' to replace deprecated 'new Integer' from BrokerToControllerRequestThreadTest Key: KAFKA-10850 URL: https://issues.apache.org/jira/browse/KAFKA-10850

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

See Changes: [github] MINOR: Make Log.recordVersion private and other small cleanups (#9731) [github] MINOR: fix typo in `AbstractIndex.scala` (#9745) --

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

Hi, I'd like to start the voting on KIP-698 that proposes an explicit user initialization of broker-side state for Kafka Streams instead of letting Kafka Streams setting up the broker-side state automatically during rebalance. Such an explicit initialization avoids possible data loss issues

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #285

See Changes: [github] MINOR: Make Log.recordVersion private and other small cleanups (#9731) -- [...truncated 3.47 MB...]