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

See Changes: [github] K7657 handling thread dead state change (#6091) -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldPassIfValueIsE

[jira] [Resolved] (KAFKA-7657) Invalid reporting of stream state in Kafka streams application

[ https://issues.apache.org/jira/browse/KAFKA-7657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7657. -- Resolution: Fixed Assignee: Guozhang Wang Fix Version/s: 2.2.0 > Invalid report

[jira] [Resolved] (KAFKA-7181) Kafka Streams State stuck in rebalancing after one of the StreamThread encounters IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7181. -- Resolution: Fixed Fix Version/s: 2.2.0 > Kafka Streams State stuck in rebalancing after

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hey Ryanne, Sorry, late to the game here. On the ACL management, can you explain how things are supposed to work when you need to migrate to the new cluster? Or is this purely for a mirroring but not DR and failover cases? In particular, the rules outlined state that only MM2 would be able to wri

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

See

Re: [DISCUSS] KIP-411: Add option to make Kafka Connect task client ID values unique

Hi Paul. I second Ewen and I intended to give similar feedback: 1) Can we avoid a config altogether? 2) If we prefer to add a config anyways, can we use a set of allowed values instead of a boolean, even if initially these values are only two? As the discussion on Jira highlights, there is a pote

[jira] [Created] (KAFKA-7788) Support null defaults in KAFKA-7609 RPC specifications

Colin P. McCabe created KAFKA-7788: -- Summary: Support null defaults in KAFKA-7609 RPC specifications Key: KAFKA-7788 URL: https://issues.apache.org/jira/browse/KAFKA-7788 Project: Kafka Issu

[jira] [Created] (KAFKA-7787) Add error specifications to KAFKA-7609

Colin P. McCabe created KAFKA-7787: -- Summary: Add error specifications to KAFKA-7609 Key: KAFKA-7787 URL: https://issues.apache.org/jira/browse/KAFKA-7787 Project: Kafka Issue Type: Improvem

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

Thanks so much Harsha and Jason! Will address the comment and make it a tuple. Get Outlook for iOS From: Jason Gustafson Sent: Friday, January 4, 2019 3:50 PM To: dev Subject: Re: [VOTE] KIP-345: Introduce static membership protocol to redu

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

See Changes: [wangguoz] KAFKA-7110: Add windowed changelog serde (#5307) -- [...truncated 4.50 MB...] > Task :streams:upgrade-system-tests-0110:processResources NO-SOURCE

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

See

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

Hey Boyang, I had just a follow-up to my comment above. I wanted to suggest an alternative schema for LeaveGroup: LeaveGroupRequest => GroupId [GroupInstanceId MemberId] So we have a single array instead of two arrays. Each element identifies a single member. For dynamic members, we would use Gr

Re: [DISCUSS] KIP-408: Add Asynchronous Processing to Kafka Streams

Hi all, Just want to hear some opinions on this KIP from the PMCs. It would be nice if we got input from them. Don't want to drag this KIP for too long! :) Hope we get some input :) Thanks, Richard On Thu, Jan 3, 2019 at 8:26 PM Richard Yu wrote: > Hi Boyang, > > Interesting article. Although

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

Thanks Guozhang and Matthias! https://github.com/apache/kafka/pull/5307 is merged now. We can close this thread now since we have a total of 3 binding votes (and 3 additional non-binding votes). On Fri, Jan 4, 2019 at 11:59 AM Guozhang Wang wrote: > Hello Shawn, > > Could you close this voting

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

See Changes: [github] KAFKA-6928: Refactor StreamsPartitionAssignor retry logic (#6085) -- [...truncated 2.26 MB...] org.apache.kafka.connect.json.JsonConverterTest > ti

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

Thanks Guozhang for the proposal! The update is done. From: Guozhang Wang Sent: Saturday, January 5, 2019 3:33 AM To: dev Subject: Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances Hello Boyang, I've made another pass on the

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

See Changes: [github] KAFKA-6928: Refactor StreamsPartitionAssignor retry logic (#6085) -- [...truncated 2.25 MB...] org.apache.kafka.connect.transforms.SetSchemaMetadataT

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

Hello Shawn, Could you close this voting thread with a tally on the votes (you can search for other voting threads as a reference)? Guozhang On Wed, Dec 19, 2018 at 1:15 AM Matthias J. Sax wrote: > Sorry for the delay. Needed to read the KIP and code multiple times to > wrap my head around it

[jira] [Resolved] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-4835. Resolution: Fixed > Allow users control over repartitioning > -

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

Hello Boyang, I've made another pass on the wiki page again. One minor comment is on the "Server Behavior Changes" section, we should have a paragraph on the logical changes on handling new versions of LeaveGroupRequest (e.g. how to handle dynamic member v.s. static member etc). Other than that,

Re: Suggestion to make 0 grace period the default for suppress

I share the compatibility concerns, and I'm more concerned about having complicated default value rules like "if suppression is used ... default value X, otherwise ... default value Y", and thus I said if we would ever consider changing it, we should avoid such situations. Another way to reduce us

[jira] [Resolved] (KAFKA-6928) StreamsPartitionAssignor is double retrying within InternalTopicManager

[ https://issues.apache.org/jira/browse/KAFKA-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6928. -- Resolution: Fixed Fix Version/s: 2.1.1 2.2.0 > StreamsPartitionAssign

Re: [VOTE] KIP-382 MirrorMaker 2.0

Hi, Ryanne, Thanks for KIP. Still have a few more comments below. 100. "This is not possible with MirrorMaker today -- records would be replicated back and forth indefinitely, and the topics in either cluster would be merged inconsistently between clusters. " This is not 100% true since MM can d

Re: [DISCUSS] KIP-411: Add option to make Kafka Connect task client ID values unique

Hi Paul, Thanks for the KIP. A few comments. To me, biggest question here is if we can fix this behavior without adding a config. In particular, today, we don't even set the client.id for the producer and consumer at all, right? The *only* way it is set is if you include an override in the worker

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

See

[jira] [Resolved] (KAFKA-7580) Unit Test 'shouldThrowProcessorStateExceptionOnOpeningReadOnlyDir' fails when run as root user

[ https://issues.apache.org/jira/browse/KAFKA-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarvesh Tamba resolved KAFKA-7580. -- Resolution: Won't Fix Refer PR [https://github.com/apache/kafka/pull/6020] for more details on

[jira] [Resolved] (KAFKA-7752) zookeeper-security-migration.sh does not remove ACL on kafka-acl-extended

[ https://issues.apache.org/jira/browse/KAFKA-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7752. -- Resolution: Fixed Fix Version/s: 2.2.0 Issue resolved by pull request 6072 [https://github.com/a