[jira] [Resolved] (KAFKA-8973) Give user options to turn off linger.ms/batch.size constraint

[ https://issues.apache.org/jira/browse/KAFKA-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8973. Resolution: Won't Fix > Give user options to turn off linger.ms/batch.size co

Re: group.instance.id for StickyAssignors

Hey Georg, thanks for your interest. We do have an open ticket for that task: https://issues.apache.org/jira/browse/KAFKA-8432, and we believe it's something worth doing just didn't get chance to implement. Feel free to take it if you want. Guozhang and Matthias, could you share your opinion o

[jira] [Created] (KAFKA-8993) Add an EOS performance test suite similar to ProducerPerformance

Boyang Chen created KAFKA-8993: -- Summary: Add an EOS performance test suite similar to ProducerPerformance Key: KAFKA-8993 URL: https://issues.apache.org/jira/browse/KAFKA-8993 Project: Kafka

[jira] [Created] (KAFKA-8989) Embedded broker could not be reached in unit test

Boyang Chen created KAFKA-8989: -- Summary: Embedded broker could not be reached in unit test Key: KAFKA-8989 URL: https://issues.apache.org/jira/browse/KAFKA-8989 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8973) Give user options to turn off linger.ms/batch.size constraint

Boyang Chen created KAFKA-8973: -- Summary: Give user options to turn off linger.ms/batch.size constraint Key: KAFKA-8973 URL: https://issues.apache.org/jira/browse/KAFKA-8973 Project: Kafka

[jira] [Created] (KAFKA-8972) Reduce streams_broker_bounce_test.py#test_broker_type_bounce flakiness

Boyang Chen created KAFKA-8972: -- Summary: Reduce streams_broker_bounce_test.py#test_broker_type_bounce flakiness Key: KAFKA-8972 URL: https://issues.apache.org/jira/browse/KAFKA-8972 Project: Kafka

Re: [VOTE] KIP-447: Producer scalability for exactly once semantics

Bump this thread to see if someone could also review! On Mon, Sep 9, 2019 at 5:00 PM Boyang Chen wrote: > Thank you Jason! Addressed the comments. > > Thank you Guozhang for explaining. I will document the timeout setting > reasoning in the design doc. > > > On Mon, S

[jira] [Resolved] (KAFKA-7018) persist memberId for consumer restart

[ https://issues.apache.org/jira/browse/KAFKA-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-7018. Fix Version/s: 2.4.0 Resolution: Fixed > persist memberId for consumer rest

[jira] [Resolved] (KAFKA-8222) Admin client changes to add ability to batch remove static members

[ https://issues.apache.org/jira/browse/KAFKA-8222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8222. Resolution: Fixed > Admin client changes to add ability to batch remove static memb

Re: [VOTE] KIP-520: Augment Consumer.committed(partition) to allow multiple partitions

Hey Guozhang, LGTM, +1 (non-binding) On Mon, Sep 9, 2019 at 5:07 PM Guozhang Wang wrote: > Hello folks, > > I've created a new KIP allowing consumer.committed to take a set of > partitions instead of just one partition to allow batching effects of such > requests (the protocol already allows us

Re: [VOTE] KIP-447: Producer scalability for exactly once semantics

Thank you Jason! Addressed the comments. Thank you Guozhang for explaining. I will document the timeout setting reasoning in the design doc. On Mon, Sep 9, 2019 at 1:49 PM Guozhang Wang wrote: > On Fri, Sep 6, 2019 at 6:33 PM Boyang Chen > wrote: > > > Thanks Guozhang, I ha

Re: [VOTE] KIP-447: Producer scalability for exactly once semantics

27;s correct, I could add a side-note to the upgrade path, although I think most people would like to pay the cost of 2 rolling bounces for the sake of consistency :) > Thanks, > Jason > > On Fri, Sep 6, 2019 at 6:33 PM Boyang Chen > wrote: > > > Thanks Guozhang, I have

Re: [VOTE] KIP-447: Producer scalability for exactly once semantics

> > Guozhang > > > > On Thu, Sep 5, 2019 at 5:47 PM Guozhang Wang wrote: > > > Thanks Boyang, I'm +1 on the KIP. > > > > Could you also update the detailed design doc > > > https://docs.google.com/document/d/1LhzHGeX7_Lay4xvrEXxfciuDWATjpUXQhrEIkph9qRE/e

[VOTE] KIP-447: Producer scalability for exactly once semantics

Hey all, I would like to start the vote for KIP-447 . This is a very important step to improve Kafka Streams scalability in exactly-once semantics, by avoiding linearly increasing number o

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

day. In the meantime, still feel free to make comments on the discussion thread, thank you! Boyang On Sun, Aug 25, 2019 at 11:43 PM Boyang Chen wrote: > Hey Guozhang and Jason, > > I'm ok with either way. Thinking of Guozhang's approach, it is simpler to > implement a cons

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

overload. > > Then usage looks something like this: > > > > consumer.subscribe(topics, new RebalanceListener() { > > void onGroupJoined(GroupMetadata metadata) { > > producer.initTransactions(metadata); > > } > > } > > > > That seems

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

Guozhang > > On Mon, Aug 12, 2019 at 3:41 PM Boyang Chen > wrote: > > > Thanks Jason, the intuition behind defining a separate callback function > is > > that, with KIP-429 we no longer guarantee to call OnPartitionsAssigned() > or > > OnPartitionsRevoked() with eac

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

if it > would make sense to overload `onPartitionsAssigned`. If it's separate, > maybe a name like `onGroupJoined` would be clearer? > > Thanks, > Jason > > > > On Thu, Aug 8, 2019 at 10:59 PM Boyang Chen > wrote: > > > Thank you Jason. We had some offline discussion on

[jira] [Created] (KAFKA-8785) Flakey test LeaderElectionCommandTest#testPathToJsonFile

Boyang Chen created KAFKA-8785: -- Summary: Flakey test LeaderElectionCommandTest#testPathToJsonFile Key: KAFKA-8785 URL: https://issues.apache.org/jira/browse/KAFKA-8785 Project: Kafka Issue

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

consumer. I was mostly just > thinking it would be better to reduce the integration point to its minimum. > Have you thought through the implications of needing to keep around a > reference to the consumer in the producer? What if it gets closed? It seems > better not to have to think abou

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

APIs are in use. What do you think? > Yes, I think we haven't covered this case, so the plan is to crash the non-stream application when the job is using new sendOffsets API. > > -Jason > > > > > On Mon, Aug 5, 2019 at 6:06 PM Boyang Chen > wrote: > > &

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

. > > Maybe we can consider having an extended class of ConsumerGroupMetadata > whose values are updated from the consumer's rebalance callback? > > > Guozhang > > > On Mon, Aug 5, 2019 at 9:26 AM Boyang Chen > wrote: > > > Thank you Guozhang for the rep

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

k already has a public class named > (ConsumerGroupMetadata) > under o.a.k.clients.consumer created by KIP-429. If we want to just use > that then maybe it makes less sense to declare a base GroupMetadata as we > are already leaking such information on the assignor anyways. > > > Guozhang > > O

Re: [DISCUSS] KIP-500: Replace ZooKeeper with a Self-Managed Metadata Quorum

clear in the KIP 500 > description. > > Ismael > > On Sat, Aug 3, 2019 at 9:32 AM Boyang Chen > wrote: > > > Thanks Colin for initiating this important effort! > > > > One question I have is whether we have a session discussing the > controller > >

Re: [DISCUSS] KIP-500: Replace ZooKeeper with a Self-Managed Metadata Quorum

Thanks Colin for initiating this important effort! One question I have is whether we have a session discussing the controller failover in the new architecture? I know we are using Raft protocol to failover, yet it's still valuable to discuss the steps new cluster is going to take to reach the stab

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

Thank you Guozhang for the reply. We will consider the interface change from 429 as a backup plan for 447. And bumping this thread for more discussion. On Mon, Jul 22, 2019 at 6:28 PM Guozhang Wang wrote: > On Sat, Jul 20, 2019 at 9:50 AM Boyang Chen > wrote: > > > Thank you G

[jira] [Resolved] (KAFKA-8435) Replace DeleteGroups request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8435. Resolution: Fixed > Replace DeleteGroups request/response with automated proto

[jira] [Created] (KAFKA-8723) flaky test LeaderElectionCommandTest#testAllTopicPartition

Boyang Chen created KAFKA-8723: -- Summary: flaky test LeaderElectionCommandTest#testAllTopicPartition Key: KAFKA-8723 URL: https://issues.apache.org/jira/browse/KAFKA-8723 Project: Kafka Issue

[jira] [Created] (KAFKA-8720) Flakey test AdminClientIntegrationTest #testElectUncleanLeadersForManyPartitions

Boyang Chen created KAFKA-8720: -- Summary: Flakey test AdminClientIntegrationTest #testElectUncleanLeadersForManyPartitions Key: KAFKA-8720 URL: https://issues.apache.org/jira/browse/KAFKA-8720 Project

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

hat > current proposal does not `generationId` since with the cooperative sticky > assignor we think it is not necessary for correctness, but also if we agree > it is okay to expose it we can potentially include it in > `ConsumerAssignmentData` as well. > > > Guozhang > > >

[jira] [Created] (KAFKA-8693) Flakey test ErrorHandlingIntegrationTest #testSkipRetryAndDLQWithHeaders

Boyang Chen created KAFKA-8693: -- Summary: Flakey test ErrorHandlingIntegrationTest #testSkipRetryAndDLQWithHeaders Key: KAFKA-8693 URL: https://issues.apache.org/jira/browse/KAFKA-8693 Project: Kafka

[jira] [Created] (KAFKA-8691) Flakey test ProcessorContextTest#shouldNotAllowToScheduleZeroMillisecondPunctuation

Boyang Chen created KAFKA-8691: -- Summary: Flakey test ProcessorContextTest#shouldNotAllowToScheduleZeroMillisecondPunctuation Key: KAFKA-8691 URL: https://issues.apache.org/jira/browse/KAFKA-8691

[jira] [Created] (KAFKA-8690) Flakey test ConnectWorkerIntegrationTest#testAddAndRemoveWorke

Boyang Chen created KAFKA-8690: -- Summary: Flakey test ConnectWorkerIntegrationTest#testAddAndRemoveWorke Key: KAFKA-8690 URL: https://issues.apache.org/jira/browse/KAFKA-8690 Project: Kafka

[jira] [Created] (KAFKA-8686) Flakey test ExampleConnectIntegrationTest#testSinkConnector

Boyang Chen created KAFKA-8686: -- Summary: Flakey test ExampleConnectIntegrationTest#testSinkConnector Key: KAFKA-8686 URL: https://issues.apache.org/jira/browse/KAFKA-8686 Project: Kafka Issue

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

API, it > would silently revert to reading the old data. Basically it would be up to > the streams version probing logic to ensure that the expectation on this > API fits with the usage of `transctional.id`. > > Sounds like a better naming to me, while I think it could be shortened to `await_tra

Re: [DISCUSS] KIP-444: Augment Metrics for Kafka Streams

I mean the partition time. On Thu, Jul 18, 2019 at 11:29 AM Guozhang Wang wrote: > Hi Boyang, > > What do you mean by `per partition latency`? > > Guozhang > > On Mon, Jul 1, 2019 at 9:28 AM Boyang Chen > wrote: > > > Hey Guozhang, > > > > do we

[jira] [Resolved] (KAFKA-8685) groupInstanceId should be encoded within the consumer protocol

[ https://issues.apache.org/jira/browse/KAFKA-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8685. Resolution: Fixed Close this because in fact we pass the instance id from join group response

[jira] [Created] (KAFKA-8685) groupInstanceId should be encoded within the consumer protocol

Boyang Chen created KAFKA-8685: -- Summary: groupInstanceId should be encoded within the consumer protocol Key: KAFKA-8685 URL: https://issues.apache.org/jira/browse/KAFKA-8685 Project: Kafka

[jira] [Created] (KAFKA-8683) Flakey test InternalTopicManagerTest @shouldNotCreateTopicIfExistsWithDifferentPartitions

Boyang Chen created KAFKA-8683: -- Summary: Flakey test InternalTopicManagerTest @shouldNotCreateTopicIfExistsWithDifferentPartitions Key: KAFKA-8683 URL: https://issues.apache.org/jira/browse/KAFKA-8683

[jira] [Created] (KAFKA-8678) LeaveGroup request versioning on throttle time is incorrect

Boyang Chen created KAFKA-8678: -- Summary: LeaveGroup request versioning on throttle time is incorrect Key: KAFKA-8678 URL: https://issues.apache.org/jira/browse/KAFKA-8678 Project: Kafka Issue

[jira] [Created] (KAFKA-8677) Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

Boyang Chen created KAFKA-8677: -- Summary: Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl Key: KAFKA-8677 URL: https://issues.apache.org/jira/browse/KAFKA-8677

[jira] [Resolved] (KAFKA-8424) Replace ListGroups request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8424. Resolution: Fixed > Replace ListGroups request/response with automated proto

Re: PR builds stopped since 07/10 11AM

ght way to proceed here. Unfortunately none of the > > JIRAs below are for the right project. > > > > Ismael > > > > On Wed, Jul 10, 2019, 5:09 PM Boyang Chen > > wrote: > > > >> Hey there, > >> > >> just want you to be aware that a

PR builds stopped since 07/10 11AM

Hey there, just want you to be aware that all the Jenkins PR builds are stopped since today's morning: https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/ https://builds.apache.org/job/kafka-pr-jdk11-scala2.12/ I have filed two JIRAs https://issues.apache.org/jira/browse/INFRATEST1-10 and ht

[jira] [Resolved] (KAFKA-8636) Document behavior change for static members with `max.poll.interval.ms`

[ https://issues.apache.org/jira/browse/KAFKA-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8636. Resolution: Fixed > Document behavior change for static members with `max.poll.interval

[jira] [Created] (KAFKA-8652) Jenkins stop triggering tests for prs since 07/10

Boyang Chen created KAFKA-8652: -- Summary: Jenkins stop triggering tests for prs since 07/10 Key: KAFKA-8652 URL: https://issues.apache.org/jira/browse/KAFKA-8652 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8645) Flakey test SaslSslAdminClientIntegrationTest#testElectUncleanLeadersAndNoop

Boyang Chen created KAFKA-8645: -- Summary: Flakey test SaslSslAdminClientIntegrationTest#testElectUncleanLeadersAndNoop Key: KAFKA-8645 URL: https://issues.apache.org/jira/browse/KAFKA-8645 Project

[jira] [Resolved] (KAFKA-8642) Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms`

[ https://issues.apache.org/jira/browse/KAFKA-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8642. Resolution: Invalid Synced with [~hachikuji], the session timeout should always be smaller than

[jira] [Created] (KAFKA-8643) Incompatible MemberDescription constructor change

Boyang Chen created KAFKA-8643: -- Summary: Incompatible MemberDescription constructor change Key: KAFKA-8643 URL: https://issues.apache.org/jira/browse/KAFKA-8643 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8642) Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms`

Boyang Chen created KAFKA-8642: -- Summary: Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms` Key: KAFKA-8642 URL: https://issues.apache.org/jira/browse/KAFKA-8642 Project

[jira] [Created] (KAFKA-8640) Replace OffsetFetch request/response with automated protocol

Boyang Chen created KAFKA-8640: -- Summary: Replace OffsetFetch request/response with automated protocol Key: KAFKA-8640 URL: https://issues.apache.org/jira/browse/KAFKA-8640 Project: Kafka

[jira] [Created] (KAFKA-8639) Replace AddPartitionsToTxn request/response with automated protocol

Boyang Chen created KAFKA-8639: -- Summary: Replace AddPartitionsToTxn request/response with automated protocol Key: KAFKA-8639 URL: https://issues.apache.org/jira/browse/KAFKA-8639 Project: Kafka

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

know if you think this is correct. On Tue, Jul 2, 2019 at 3:21 PM Boyang Chen wrote: > Thank you Guozhang for the questions, inline answers are below. > > On Tue, Jul 2, 2019 at 3:14 PM Boyang Chen > wrote: > >> Hey all, >> >> I have done a fundamental polish o

[jira] [Created] (KAFKA-8636) Document behavior change for static members with `max.poll.interval.ms`

Boyang Chen created KAFKA-8636: -- Summary: Document behavior change for static members with `max.poll.interval.ms` Key: KAFKA-8636 URL: https://issues.apache.org/jira/browse/KAFKA-8636 Project: Kafka

[jira] [Created] (KAFKA-8626) Group will fall into constant incremental rebalancing with a long non-responsive static member

Boyang Chen created KAFKA-8626: -- Summary: Group will fall into constant incremental rebalancing with a long non-responsive static member Key: KAFKA-8626 URL: https://issues.apache.org/jira/browse/KAFKA-8626

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

Thank you Guozhang for the questions, inline answers are below. On Tue, Jul 2, 2019 at 3:14 PM Boyang Chen wrote: > Hey all, > > I have done a fundamental polish of KIP-447 > <https://cwiki.apache.org/confluence/display/KAFKA/KIP-447%3A+Producer+scalability+for+exactly+once+se

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

; think > > it is reasonable to expose from AdminClient. It can be used by management > > tools to inspect running Kafka versions for example. > > > > -Jason > > > > On Tue, Jun 25, 2019 at 4:37 PM Boyang Chen > > wrote: > > > > > Thank you fo

[jira] [Created] (KAFKA-8620) Fix potential race condition in StreamThread state change

Boyang Chen created KAFKA-8620: -- Summary: Fix potential race condition in StreamThread state change Key: KAFKA-8620 URL: https://issues.apache.org/jira/browse/KAFKA-8620 Project: Kafka Issue

Re: [DISCUSS] KIP-444: Augment Metrics for Kafka Streams

Hey Guozhang, do we plan to add per partition latency in this KIP? On Mon, Jul 1, 2019 at 7:08 AM Bruno Cadonna wrote: > Hi Guozhang, > > Thank you for the KIP. > > 1) As far as I understand, the StreamsMetrics interface is there for > user-defined processors. Would it make sense to also add a

[jira] [Created] (KAFKA-8618) Replace WriteTxnMarkers request/response with automated protocol

Boyang Chen created KAFKA-8618: -- Summary: Replace WriteTxnMarkers request/response with automated protocol Key: KAFKA-8618 URL: https://issues.apache.org/jira/browse/KAFKA-8618 Project: Kafka

[jira] [Created] (KAFKA-8617) Replace EndTxn request/response with automated protocol

Boyang Chen created KAFKA-8617: -- Summary: Replace EndTxn request/response with automated protocol Key: KAFKA-8617 URL: https://issues.apache.org/jira/browse/KAFKA-8617 Project: Kafka Issue Type

[jira] [Created] (KAFKA-8616) Replace ApiVersionsRequest request/response with automated protocol

Boyang Chen created KAFKA-8616: -- Summary: Replace ApiVersionsRequest request/response with automated protocol Key: KAFKA-8616 URL: https://issues.apache.org/jira/browse/KAFKA-8616 Project: Kafka

[jira] [Resolved] (KAFKA-8569) Integrate the poll timeout warning with leave group call

[ https://issues.apache.org/jira/browse/KAFKA-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8569. Resolution: Fixed > Integrate the poll timeout warning with leave group c

[jira] [Resolved] (KAFKA-8356) Add static membership to Round Robin assignor

[ https://issues.apache.org/jira/browse/KAFKA-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8356. Resolution: Fixed > Add static membership to Round Robin assig

[jira] [Resolved] (KAFKA-8538) Add `group.instance.id` to DescribeGroup for better visibility

[ https://issues.apache.org/jira/browse/KAFKA-8538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8538. Resolution: Fixed > Add `group.instance.id` to DescribeGroup for better visibil

Re: [VOTE] KIP-429: Kafka Consumer Incremental Rebalance Protocol

:37 PM, Harsha wrote: > > > > +1 (binding). Thanks for the KIP looking forward for this to be > > avaiable > > > in consumers. > > > > > > > > Thanks, > > > > Harsha > > > > > > > > On Wed, May 22,

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

he/kafka/pull/3012 . However, we started to > rethink whether this AdminClient function was even necessary. Most of the > use-cases we could think of seemed like horrible hacks. So it has never > really been implemented (yet?). > > best, > Colin > > > On Tue, Jun 25, 2019,

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

, 2019 at 2:57 PM Boyang Chen wrote: > Thank you Guozhang, some of my understandings are inline below. > > On Tue, Jun 25, 2019 at 11:05 AM Jason Gustafson > wrote: > >> > >> > I think co-locating does have some merits here, i.e. letting the >> > Consume

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

ersion metadata to > > Coordinator, so that Coordinator can rely on that logic to change its > > behavior dynamically. > The stream thread init could not be supported by a client coordinator behavior change on the fly, we are only losing possibilities after we initialized. (main thr

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

e other sort of "resources" based on > > the > > > source systems, how KIP-447 would affect Kafka Connectors that > > implemented > > > EOS as well? > > > > > > > No, it's not currently included in the scope. Could you point me

Re: [DISCUSS] KIP-480 : Sticky Partitioner

Thank you Justine for the KIP! Do you mind creating a corresponding JIRA ticket too? On Mon, Jun 24, 2019 at 4:51 PM Colin McCabe wrote: > Hi Justine, > > Thanks for the KIP. This looks great! > > In one place in the KIP, you write: "Remove > testRoundRobinWithUnavailablePartitions() and testRo

Re: [DISCUSS] KIP-447: Producer scalability for exactly once semantics

d and let topic partition and connect task implement it. > > Guozhang > > > On Sat, Jun 22, 2019 at 8:40 PM Ismael Juma wrote: > > > Hi Boyang, > > > > Thanks for the KIP. It's good that we listed a number of rejected > > alternatives. It would be helpful to

[jira] [Created] (KAFKA-8590) Replace TxnOffsetCommitRequest request/response with automated protocol

Boyang Chen created KAFKA-8590: -- Summary: Replace TxnOffsetCommitRequest request/response with automated protocol Key: KAFKA-8590 URL: https://issues.apache.org/jira/browse/KAFKA-8590 Project: Kafka

[jira] [Created] (KAFKA-8589) Flakey test ResetConsumerGroupOffsetTest#testResetOffsetsExistingTopic

Boyang Chen created KAFKA-8589: -- Summary: Flakey test ResetConsumerGroupOffsetTest#testResetOffsetsExistingTopic Key: KAFKA-8589 URL: https://issues.apache.org/jira/browse/KAFKA-8589 Project: Kafka

[DISCUSS] KIP-447: Producer scalability for exactly once semantics

Hey all, I would like to start a discussion for KIP-447: https://cwiki.apache.org/confluence/display/KAFKA/KIP-447%3A+Producer+scalability+for+exactly+once+semantics this is a work originated by Jason Gustafson and we would like to proceed into discussion stage. Let me know your thoughts, thank

[jira] [Created] (KAFKA-8587) EOS producer should understand consumer group assignment semantics

Boyang Chen created KAFKA-8587: -- Summary: EOS producer should understand consumer group assignment semantics Key: KAFKA-8587 URL: https://issues.apache.org/jira/browse/KAFKA-8587 Project: Kafka

[jira] [Resolved] (KAFKA-7857) Add AbstractCoordinatorConfig class to consolidate consumer coordinator configs between Consumer and Connect

[ https://issues.apache.org/jira/browse/KAFKA-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-7857. Resolution: Fixed [https://github.com/apache/kafka/pull/6854] fixes it >

[jira] [Created] (KAFKA-8569) Integrate the poll timeout warning with leave group call

Boyang Chen created KAFKA-8569: -- Summary: Integrate the poll timeout warning with leave group call Key: KAFKA-8569 URL: https://issues.apache.org/jira/browse/KAFKA-8569 Project: Kafka Issue

[jira] [Resolved] (KAFKA-8500) member.id should always update upon static member rejoin despite of group state

[ https://issues.apache.org/jira/browse/KAFKA-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8500. Resolution: Fixed > member.id should always update upon static member rejoin despite of gr

Re: Preliminary blog post for the Apache Kafka 2.3.0 release

One typo: KIP-428: Add in-mbmory window store should be KIP-428: Add in-memory window store From: Colin McCabe Sent: Wednesday, June 19, 2019 4:22 AM To: dev@kafka.apache.org Subject: Re: Preliminary blog post for the Apache Kafka 2.3.0 release Sorry, I copied t

[jira] [Reopened] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen reopened KAFKA-4222: Assignee: (was: Damian Guy) > Transient failure

[jira] [Created] (KAFKA-8556) Add system tests for assignment stickiness validation

Boyang Chen created KAFKA-8556: -- Summary: Add system tests for assignment stickiness validation Key: KAFKA-8556 URL: https://issues.apache.org/jira/browse/KAFKA-8556 Project: Kafka Issue Type

[jira] [Created] (KAFKA-8555) Flaky test ExampleConnectIntegrationTest#testSourceConnector

Boyang Chen created KAFKA-8555: -- Summary: Flaky test ExampleConnectIntegrationTest#testSourceConnector Key: KAFKA-8555 URL: https://issues.apache.org/jira/browse/KAFKA-8555 Project: Kafka

[jira] [Resolved] (KAFKA-7853) Refactor ConsumerCoordinator/AbstractCoordinator to reduce constructor parameter list

[ https://issues.apache.org/jira/browse/KAFKA-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-7853. Resolution: Fixed > Refactor ConsumerCoordinator/AbstractCoordinator to reduce construc

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

, June 14, 2019 8:42 PM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id Hi Boyang, Thanks for the update. To what extent will KIP-345 be available in 2.3.0? Mike On 6/13/19, 5:36 PM, "Boyang Chen" wrote: Hey al

[jira] [Created] (KAFKA-8541) Flakey test LeaderElectionCommandTest#testTopicPartition

Boyang Chen created KAFKA-8541: -- Summary: Flakey test LeaderElectionCommandTest#testTopicPartition Key: KAFKA-8541 URL: https://issues.apache.org/jira/browse/KAFKA-8541 Project: Kafka Issue

[jira] [Created] (KAFKA-8539) Add `getGroupInstanceId` call to Subscription class

Boyang Chen created KAFKA-8539: -- Summary: Add `getGroupInstanceId` call to Subscription class Key: KAFKA-8539 URL: https://issues.apache.org/jira/browse/KAFKA-8539 Project: Kafka Issue Type

[jira] [Created] (KAFKA-8538) Add `group.instance.id` to DescribeGroup for better visibility

Boyang Chen created KAFKA-8538: -- Summary: Add `group.instance.id` to DescribeGroup for better visibility Key: KAFKA-8538 URL: https://issues.apache.org/jira/browse/KAFKA-8538 Project: Kafka

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

any concerns. Best, Boyang From: Boyang Chen Sent: Friday, April 26, 2019 11:16 AM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id Hey all, there is a minor change to the stream side logic for

[jira] [Resolved] (KAFKA-8223) Deprecate group.initial.rebalance.delay

[ https://issues.apache.org/jira/browse/KAFKA-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8223. Resolution: Later > Deprecate group.initial.rebalance.de

[jira] [Created] (KAFKA-8529) Flakey test ConsumerBounceTest#testCloseDuringRebalance

Boyang Chen created KAFKA-8529: -- Summary: Flakey test ConsumerBounceTest#testCloseDuringRebalance Key: KAFKA-8529 URL: https://issues.apache.org/jira/browse/KAFKA-8529 Project: Kafka Issue Type

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

Hey Colin and Jason, I would like to mention that https://issues.apache.org/jira/browse/KAFKA-8500 could also potentially be a blocker. The PR is ready for review: https://github.com/apache/kafka/pull/6899 Boyang From: Colin McCabe Sent: Tuesday, June 11, 2019

[jira] [Created] (KAFKA-8515) Materialize KTable when upstream uses Windowed instead of

Boyang Chen created KAFKA-8515: -- Summary: Materialize KTable when upstream uses Windowed instead of Key: KAFKA-8515 URL: https://issues.apache.org/jira/browse/KAFKA-8515 Project: Kafka Issue

[jira] [Created] (KAFKA-8502) Flakey test AdminClientIntegrationTest#testElectUncleanLeadersForAllPartitions

Boyang Chen created KAFKA-8502: -- Summary: Flakey test AdminClientIntegrationTest#testElectUncleanLeadersForAllPartitions Key: KAFKA-8502 URL: https://issues.apache.org/jira/browse/KAFKA-8502 Project

[jira] [Created] (KAFKA-8500) member.id should always update upon static member rejoin despite of group state

Boyang Chen created KAFKA-8500: -- Summary: member.id should always update upon static member rejoin despite of group state Key: KAFKA-8500 URL: https://issues.apache.org/jira/browse/KAFKA-8500 Project

[jira] [Created] (KAFKA-8490) Use `Migrated` and `Deleted` state to replace consumer group `Dead` state

Boyang Chen created KAFKA-8490: -- Summary: Use `Migrated` and `Deleted` state to replace consumer group `Dead` state Key: KAFKA-8490 URL: https://issues.apache.org/jira/browse/KAFKA-8490 Project: Kafka

[jira] [Created] (KAFKA-8489) Remove group immediately when DeleteGroup request could be completed

Boyang Chen created KAFKA-8489: -- Summary: Remove group immediately when DeleteGroup request could be completed Key: KAFKA-8489 URL: https://issues.apache.org/jira/browse/KAFKA-8489 Project: Kafka

Re: [DISCUSS] KIP-333 Consider a faster form of rebalancing

Hey Matthias, I took a quick overview of this proposal. My impression is that the proposal lacks concrete use case to support it. For example, the goal here is to immediately resume processing the latest data being populated, then we could just reset application to point to latest offset. If t

[jira] [Resolved] (KAFKA-8445) Flaky Test UncleanLeaderElectionTest#testUncleanLeaderElectionDisabledByTopicOverride

[ https://issues.apache.org/jira/browse/KAFKA-8445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8445. Resolution: Duplicate > Flaky Test > UncleanLeaderElecti

[jira] [Created] (KAFKA-8462) flakey test RestServerTest#testCORSEnabled

Boyang Chen created KAFKA-8462: -- Summary: flakey test RestServerTest#testCORSEnabled Key: KAFKA-8462 URL: https://issues.apache.org/jira/browse/KAFKA-8462 Project: Kafka Issue Type: Bug

<    1   2   3   4   5   6   7   8   >