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

See Changes: [github] KAFKA-10144: clean up corrupted standby tasks before attempting a commit -- [...truncated 3.02 MB...] org.apache.kafka.streams.TestTopicsTest >

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

See Changes: [wangguoz] KAFKA-10144: clean up corrupted standby tasks before attempting a commit -- [...truncated 3.14 MB...]

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

See Changes: [github] KAFKA-10144: clean up corrupted standby tasks before attempting a commit -- [...truncated 3.02 MB...]

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

See Changes: [github] KAFKA-10144: clean up corrupted standby tasks before attempting a commit -- [...truncated 3.00 MB...]

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

See Changes: [github] KAFKA-9432: automated protocol for DescribeConfigs (#8312) [github] KAFKA-10157: Fix broken tests due to InterruptedException from --

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

See Changes: [github] KAFKA-9432: automated protocol for DescribeConfigs (#8312) [github] KAFKA-10157: Fix broken tests due to InterruptedException from --

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

See Changes: [github] KAFKA-9432: automated protocol for DescribeConfigs (#8312) [github] KAFKA-10157: Fix broken tests due to InterruptedException from --

[jira] [Created] (KAFKA-10158) Fix flaky kafka.admin.TopicCommandWithAdminClientTest#testDescribeUnderReplicatedPartitionsWhenReassignmentIsInProgress

Chia-Ping Tsai created KAFKA-10158: -- Summary: Fix flaky kafka.admin.TopicCommandWithAdminClientTest#testDescribeUnderReplicatedPartitionsWhenReassignmentIsInProgress Key: KAFKA-10158 URL:

Jenkins build is back to normal : kafka-2.5-jdk8 #153

See

Re: [VOTE] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Thanks Colin for the suggestions! On Fri, Jun 12, 2020 at 2:40 PM Colin McCabe wrote: > Hi Boyang, > > Thanks for the KIP! I think it's getting close. > > > For older requests that need redirection, forwarding > > broker will just use its own authorizer to verify the principals. When > the >

Re: [VOTE] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hi Boyang, Thanks for the KIP! I think it's getting close. > For older requests that need redirection, forwarding > broker will just use its own authorizer to verify the principals. When the > request looks good, it will just forward the request with its own > credentials, no second

[jira] [Resolved] (KAFKA-10157) Multiple tests failed due to "Failed to process feature ZK node change event"

[ https://issues.apache.org/jira/browse/KAFKA-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kowshik Prakasam resolved KAFKA-10157. -- Resolution: Fixed > Multiple tests failed due to "Failed to process feature ZK node

Re: Broker side round robin on topic partitions when receiving messages

HI Vinicius, This question seems like a better fit for the user mailing list rather than the developer mailing list. Anyway, if I understand correctly, you are asking if the producer can choose to assign partitions in a round-robin fashion rather than based on the key. The answer is, you

Re: [DISCUSS] KIP-623: Add "internal-topics" option to streams application reset tool

Hi Bruce Thank you for the comments. I agree with 1 and 3 and have updated the KIP. 2. Yes, the user needs to execute the script twice. Once with `--dry-run` and once without. There are no confirmation prompts when executing without `--dry-run`. I have updated the KIP to make this clearer.

Re: [VOTE] KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations

+1. Thanks, David! best, Colin On Thu, Jun 11, 2020, at 23:51, David Jacot wrote: > Colin, Jun, > > Do the proposed error code and the updated KIP look good to you guys? I’d > like to wrap up and close the vote. > > Thanks, > David > > Le mer. 10 juin 2020 à 14:50, David Jacot a écrit : >

Re: [DISCUSSION] KIP-619: Add internal topic creation support

Cheng, thanks for the KIP! Can you include some details about how this will work the post-ZK world? For KafkaAdminClient, will we add a new "internal" field to NewTopic, or will we reuse the existing "configs" map. One concern with sticking this new special field in the topic configs is that we

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

See Changes: [vvcephei] KAFKA-10049: Fixed FKJ bug where wrapped serdes are set incorrectly when -- [...truncated 3.14 MB...]

Re: [DISCUSS] 2.5.1 Bug Fix Release

https://issues.apache.org/jira/browse/KAFKA-10134 looks concerning too. Ismael On Fri, Jun 12, 2020 at 10:12 AM John Roesler wrote: > Hello again, all, > > Another status update: > We have just merged the fix for blocker: > KAFKA-10049 KTable-KTable Foreign Key join throwing Serialization

Re: [DISCUSS] 2.5.1 Bug Fix Release

Hello again, all, Another status update: We have just merged the fix for blocker: KAFKA-10049 KTable-KTable Foreign Key join throwing Serialization Exception There are currently two tickets blocking the 2.5.1 release: KAFKA-9891 Invalid state store content after task migration with

Re: Kafka - entity-default Vs entity-name

Thanks Brian, that answers my question On Fri, 12 Jun, 2020, 9:16 PM Brian Byrne, wrote: > Hi Nag, > > Correct, --all will include both. Removing --all should give you only the > overridden values. > > Are you asking if you can see overridden values for a broker with both the > default config

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

Thanks for the suggestions Guozhang. On Thu, Jun 11, 2020 at 2:51 PM Guozhang Wang wrote: > Hello Boyang, > > Thanks for the updated information. A few questions here: > > 1) Should the quorum-file also update to support multi-raft? > > I'm neutral about this, as we don't know yet how the

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

See Changes: [github] KAFKA-10049: Fixed FKJ bug where wrapped serdes are set incorrectly when -- [...truncated 1.79 MB...]

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

See Changes: [github] KAFKA-10049: Fixed FKJ bug where wrapped serdes are set incorrectly when -- [...truncated 2.07 MB...] org.apache.kafka.streams.TestTopicsTest >

Re: [VOTE] KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations

Hi, David, Thanks for making those changes. They look fine to me. +1 Jun On Thu, Jun 11, 2020 at 11:51 PM David Jacot wrote: > Colin, Jun, > > Do the proposed error code and the updated KIP look good to you guys? I’d > like to wrap up and close the vote. > > Thanks, > David > > Le mer. 10

Re: Kafka - entity-default Vs entity-name

My apologies, the command mentioned should include --all: kafka-configs ... --entity-type brokers --entity-name 1 --describe --all | grep DYNAMIC Brian On Fri, Jun 12, 2020 at 8:45 AM Brian Byrne wrote: > Hi Nag, > > Correct, --all will include both. Removing --all should give you only the >

Re: Kafka - entity-default Vs entity-name

Hi Nag, Correct, --all will include both. Removing --all should give you only the overridden values. Are you asking if you can see overridden values for a broker with both the default config and specific broker config in one command? Unfortunately the commands only give you the overrides for

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

See Changes: [github] KAFKA-10049: Fixed FKJ bug where wrapped serdes are set incorrectly when -- [...truncated 2.29 MB...] org.apache.kafka.streams.MockTimeTest >

Re: [DISCUSS] KIP-623: Add "internal-topics" option to streams application reset tool

Hi Joel, Thank you for the KIP. The KIP is well motivated. I have a couple comments: 1. I would not describe the new option with Java code that you want to add to the `StreamsResetter` class since this class is not part of the public API. Only the script kafka-streams-application-reset.sh in

Re: Kafka - entity-default Vs entity-name

Thanks Brian. I applied the following command with --all, it works fine. kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 1 --describe --all. I believe this includes *both* default config values as well as config values those were overridden . Is there any

Re: Kafka - entity-default Vs entity-name

Hi Nag, To address (2) first, the --entity-default flag requests the default configuration that all brokers inherit. An individual broker may override any of the default config's entries, which is done by specifying the broker ID to the --entity-name flag. The reason you're getting blank output

Kafka - entity-default Vs entity-name

I applied kafka-config to get the default settings for the brokers, kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-default --describe The command responded with the following response, without any *complete* output. Default configs for brokers in the cluster

Kafka - Auto commit

During the time when i was going through the doc and come across , Automatic Commit The easiest way to commit offsets is to allow the consumer to do

Re: [DISCUSS] KIP-578: Add configuration to limit number of partitions

Hi Gokul, Thank you for the answers and the data provided to illustrate the use case. A couple of additional questions. 904. If multi-tenancy is addressed in a future KIP, how smooth would be the upgrade path? For example, the introduced configuration parameters still apply, right? We would

Re: [DISCUSS] KIP-623: Add "internal-topics" option to streams application reset tool

Thanks Boyang, that’s helpful! Have made the changes and updated the KIP now. Joel > On 11 Jun 2020, at 5:38 PM, Boyang Chen wrote: > > Thanks for the KIP Joel! Some quick questions and suggestions: > > 1. The KIP links to a wrong JIRA, which should be >

Re: [VOTE] KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations

Colin, Jun, Do the proposed error code and the updated KIP look good to you guys? I’d like to wrap up and close the vote. Thanks, David Le mer. 10 juin 2020 à 14:50, David Jacot a écrit : > Hi Colin and Jun, > > I have no problem if we have to rewrite part of it when the new controller >