Build failed in Jenkins: kafka-2.4-jdk8 #48

See Changes: [wangguoz] KAFKA-8972 (2.4 blocker): TaskManager state should always be updated -- [...truncated 5.08 MB...] kafka.server.KafkaConfigTest >

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

See Changes: [manikumar.reddy] MINOR: Replace some Java 7 style code with Java 8 style (#7623) [wangguoz] MINOR: Fix sensor retrieval in stand0by task's constructor (#7632) [bbejeck] MINOR: Fix Kafka Streams

Re: [VOTE] KIP-545 support automated consumer offset sync across clusters in MM 2.0

I think this kip will implement a task in sinkTask ? right? On Sat, Nov 2, 2019 at 1:06 AM Ryanne Dolan wrote: > Hey y'all, Ning Zhang and I would like to start the vote for the following > small KIP: > > >

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

See Changes: [bbejeck] MINOR: Fix Kafka Streams JavaDocs with regard to new StreamJoined class [wangguoz] KAFKA-8972 (2.4 blocker): TaskManager state should always be updated

[jira] [Resolved] (KAFKA-9080) System Test Failure: MessageFormatChangeTest.testCompatibilty

[ https://issues.apache.org/jira/browse/KAFKA-9080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-9080. -- Resolution: Fixed > System Test Failure: MessageFormatChangeTest.testCompatibilty >

Re: [VOTE] KIP-541: Create a fetch.max.bytes configuration for the broker

Hi all, With binding +1 votes from Ismael Juma, David Arthur, and Colin McCabe, and non-binding +1 votes from Tom Bentley and Stanislav Kozlovski, the vote passes. thanks, all. Colin On Fri, Nov 1, 2019, at 09:41, Colin McCabe wrote: > I will add my +1, binding > > best, > Colin > > On Fri,

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

See Changes: [manikumar.reddy] MINOR: Replace some Java 7 style code with Java 8 style (#7623) [wangguoz] MINOR: Fix sensor retrieval in stand0by task's constructor (#7632)

[jira] [Resolved] (KAFKA-8972) KafkaConsumer.unsubscribe could leave inconsistent user rebalance callback state

[ https://issues.apache.org/jira/browse/KAFKA-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8972. -- Resolution: Fixed > KafkaConsumer.unsubscribe could leave inconsistent user rebalance callback

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

Adding on to John's response to 3), can you clarify when and why exactly we cannot convert between taskIds and partitions? If that's really the case I don't feel confident that the StreamsPartitionAssignor is not full of bugs... It seems like it currently just encodes a list of all partitions

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

See Changes: [wangguoz] KAFKA-8868: Generate SubscriptionInfo protocol message (#7248) -- [...truncated 2.75 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

See Changes: [wangguoz] KAFKA-8868: Generate SubscriptionInfo protocol message (#7248) -- [...truncated 2.74 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-9132) Refactor StreamThread to take advantage of new ConsumerRebalanceListener exception handling

Sophie Blee-Goldman created KAFKA-9132: -- Summary: Refactor StreamThread to take advantage of new ConsumerRebalanceListener exception handling Key: KAFKA-9132 URL:

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

Thanks, all, for considering the points! 3. Interesting. I have a vague recollection of that... Still, though, it seems a little fishy. After all, we return the assignments themselves as task ids, and the members have to map these to topic partitions in order to configure themselves properly. If

Re: question about offsetSync

>From my opinion, condition 4 is downstream data loss because of master down without sync in time, so downstream data producer get smaller downstreamOffset. condition 3 meaning upstream broker down without sync in time condition 1 is init state so condition 2 may write like this:

[jira] [Created] (KAFKA-9131) failed producer metadata updates result in the unrelated error message

Ask Zuckerberg created KAFKA-9131: - Summary: failed producer metadata updates result in the unrelated error message Key: KAFKA-9131 URL: https://issues.apache.org/jira/browse/KAFKA-9131 Project:

question about offsetSync

Hi: I am engineer from China, I review kafka mirror latest impl, but I do not figure out the reason why PartitionState update like that: ``` // true if we should emit an offset sync boolean update(long upstreamOffset, long downstreamOffset) { boolean shouldSyncOffsets = false;

Re: [VOTE] KIP-541: Create a fetch.max.bytes configuration for the broker

I will add my +1, binding best, Colin On Fri, Nov 1, 2019, at 01:57, Stanislav Kozlovski wrote: > +1 (non-binding). > Thanks! > Stanislav > > On Fri, Oct 25, 2019 at 2:29 PM David Arthur wrote: > > > +1 binding, this will be a nice improvement. Thanks, Colin! > > > > -David > > > > On Fri,

Re: [DISCUSS] KIP-518: Allow listing consumer groups per state

Hi Tom, Thanks for taking a look at the KIP! You are right, even if we serialize the field as a String, we should use ConsumerGroupState in the API. As suggested, I've also updated the API so a list of states is specified. Regards, On Tue, Oct 22, 2019 at 10:03 AM Tom Bentley wrote: > > Hi

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

See Changes: [manikumar] MINOR: Correctly mark offset expiry in GroupMetadataManager's -- [...truncated 5.55 MB...] org.apache.kafka.streams.TestTopicsTest >

[jira] [Created] (KAFKA-9130) Allow listing consumer groups per state

Mickael Maison created KAFKA-9130: - Summary: Allow listing consumer groups per state Key: KAFKA-9130 URL: https://issues.apache.org/jira/browse/KAFKA-9130 Project: Kafka Issue Type:

Re: [DISCUSS] Apache Kafka 2.4.0 release

Hi All, We still have couple of blockers to close. PRs available for both the blockers. https://issues.apache.org/jira/browse/KAFKA-8972 https://issues.apache.org/jira/browse/KAFKA-9080 Thanks, On Fri, Oct 25, 2019 at 10:48 PM Manikumar wrote: > Hi all, > > Quick update on the 2.4

Build failed in Jenkins: kafka-2.4-jdk8 #47

See Changes: [manikumar] MINOR: Correctly mark offset expiry in GroupMetadataManager's -- [...truncated 5.06 MB...] kafka.server.LogOffsetTest >

[jira] [Created] (KAFKA-9129) Add Thread ID to the InternalProcessorContext

Bruno Cadonna created KAFKA-9129: Summary: Add Thread ID to the InternalProcessorContext Key: KAFKA-9129 URL: https://issues.apache.org/jira/browse/KAFKA-9129 Project: Kafka Issue Type:

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

See Changes: [manikumar] MINOR: Correctly mark offset expiry in GroupMetadataManager's -- [...truncated 2.74 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

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

Hi Jun, Thanks for looking into the updated KIP and clarifying our earlier queries. >20. It's fine to keep the HDFS binding temporarily in the PR. We just need to remove it before it's merged to trunk. As Victor mentioned, we can provide a reference implementation based on a mocked version of

Re: [DISCUSS] KIP-536: Propagate broker timestamp to Admin API

Hey Noa, KIP-436 added a JMX metric in Kafka for this exact use-case, called `start-time-ms`. Perhaps it would be useful to name this public interface in the same way for consistency. Could you update the KIP to include the specific RPC changes regarding the metadata request/responses? Here is a

Re: [VOTE] KIP-541: Create a fetch.max.bytes configuration for the broker

+1 (non-binding). Thanks! Stanislav On Fri, Oct 25, 2019 at 2:29 PM David Arthur wrote: > +1 binding, this will be a nice improvement. Thanks, Colin! > > -David > > On Fri, Oct 25, 2019 at 4:33 AM Tom Bentley wrote: > > > +1 nb. Thanks! > > > > On Fri, Oct 25, 2019 at 7:43 AM Ismael Juma

Re: [DISCUSS] KIP-542: Partition Reassignment Throttling

Hey Viktor. Thanks for the KIP! > We will introduce two new configs in order to eventually replace *.replication.throttled.rate. Just to clarify, you mean to replace said config in the context of reassignment throttling, right? We are not planning to remove that config And also to clarify,

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

See

[jira] [Created] (KAFKA-9128) ConsumerCoordinator ignores exceptions from ConsumerRebalanceListener

Oleg Muravskiy created KAFKA-9128: - Summary: ConsumerCoordinator ignores exceptions from ConsumerRebalanceListener Key: KAFKA-9128 URL: https://issues.apache.org/jira/browse/KAFKA-9128 Project: Kafka

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

See