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

Hey Mayuresh, thanks for giving another thorough thought on this matter! The session timeout is controlled on the member level (or more specifically member.id level), which has nothing to do with the static member mapping. Putting aside the low possibility of having a duplicate member id assign

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hi Ryanne, Thanks for the reply. You are right. The topic naming and ACL sanity check should probably be a separate discussion. Regarding the offset mapping. Thought about this a bit more. We may need to consider the cases such as logs including transactional messages. In that case, the offset ma

Build failed in Jenkins: kafka-2.1-jdk8 #91

See Changes: [jason] MINOR: Improve exception messages in FileChannelRecordBatch (#6068) -- [...truncated 463.04 KB...] kafka.api.GroupAuthorizerIntegrationTest > testUnauthor

Build failed in Jenkins: kafka-2.0-jdk8 #208

See Changes: [jason] MINOR: Improve exception messages in FileChannelRecordBatch (#6068) -- [...truncated 436.74 KB...] kafka.zk.ReassignPartitionsZNodeTest > testDecodeValid

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

See Changes: [jason] MINOR: Improve exception messages in FileChannelRecordBatch (#6068) -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest > s

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Yep Stanislav, that's what I'm proposing, and your explanation makes sense. Boyang From: Stanislav Kozlovski Sent: Friday, December 28, 2018 7:59 PM To: dev@kafka.apache.org Subject: Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth He

Build failed in Jenkins: kafka-2.0-jdk8 #207

See Changes: [jason] KAFKA-3832; Kafka Connect's JSON Converter never outputs a null value -- [...truncated 2.66 MB...] org.apache.kafka.connect.runtime.WorkerSourceTaskTest

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

See Changes: [jason] KAFKA-3832; Kafka Connect's JSON Converter never outputs a null value -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Resolved] (KAFKA-3832) Kafka Connect's JSON Converter never outputs a null value

[ https://issues.apache.org/jira/browse/KAFKA-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3832. Resolution: Fixed Assignee: Renato Mefi (was: Prasanna Subburaj) Fix Versio

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Hey there everybody, let's work on wrapping this discussion up. @Boyang, could you clarify what you mean by > One more question is whether you feel we should enforce group size cap statically or on runtime? Is that related to the option of enabling this config via the dynamic broker config feature