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

See Changes: [github] KAFKA-8746: Kibosh must handle an empty JSON string from Trogdor (#7155) [github] KAFKA-9183; Remove redundant admin client integration testing (#7690)

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

See

Re: [VOTE] 2.4.0 RC0

Hello, - all PGP signatures are good - All md5, sha1sums and sha512sums pass 2648 unit test pass, 1 failure (ran twice) ClientsMetricsTest.shouldAddCommitIdMetric Failed: Java.lang.AssertionError: Unexpected method call StreamsMetricsImpl.addClientLevelImmutableMetric("commit-id", "The

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

See Changes: [ismael] MINOR. Replace Utils::readFileAsString method to read file as stream -- [...truncated 2.75 MB...] org.apache.kafka.streams.test.TestRecordTest >

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

On Tue, Nov 12, 2019, at 10:27, Brian Byrne wrote: > Hi Colin, > > Thanks for the feedback. I'm going to leave out some specifics in my > response, since I'll go back to the KIP, revise it, and then post an update > on the original discussion thread. I'll make two primary changes, (1) > remove

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

On Tue, Nov 12, 2019, at 17:42, Guozhang Wang wrote: > Sounds good to me, let's continue our voting process here. > > Guozhang Hi Brian & Guozhang, I'm looking forward to getting this in. But is the KIP complete yet? Brian's earlier response said " I'm going to leave out some specifics in my

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

See Changes: [github] KAFKA-9165: Fix jersey warnings in Trogdor (#7669) -- [...truncated 2.75 MB...] org.apache.kafka.streams.test.TestRecordTest > testProducerRecord

[jira] [Created] (KAFKA-9196) Records exposed before advancement of high watermark after segment roll

Jason Gustafson created KAFKA-9196: -- Summary: Records exposed before advancement of high watermark after segment roll Key: KAFKA-9196 URL: https://issues.apache.org/jira/browse/KAFKA-9196 Project:

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Thanks Sophie, I think your concern is valid, and also that your idea to make a ticket is a good idea. Creating a ticket has some very positive effects: * It allows us to record the thinking at this point in time so we don't have to dig through the mail archives later * It demonstrates that we

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

While I'm concerned that "not augmenting groupBy as part of this KIP" really translates to "will not get around to augmenting groupBy for a long time if not as part of this KIP", like I said I don't want to hold up the new .repartition operator that it seems we do, at least, all agree on. It's a

[jira] [Resolved] (KAFKA-9120) Convert ./bin/kafka-reassign-partitions.sh to use KIP-455

[ https://issues.apache.org/jira/browse/KAFKA-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-9120. - Resolution: Duplicate > Convert ./bin/kafka-reassign-partitions.sh to use KIP-455 >

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

Hi, Satish and Harsha, The following is a more detailed high level feedback for the KIP. Overall, the KIP seems useful. The challenge is how to design it such that it’s general enough to support different ways of implementing this feature and support existing features. 40. Local segment metadata

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hi all, I think that Sophie is asking a good question, and I do think that such "blanket configurations" are plausible. For example, we currently support (and I would encourage) "I don't know if this is going to create a repartition topic, but if it does, then use this name instead of generating

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

I'm +1 (binding) as well. Thanks, -John On Fri, Nov 15, 2019 at 6:20 AM Bill Bejeck wrote: > > +1 (binding) > > On Fri, Nov 15, 2019 at 1:11 AM Matthias J. Sax > wrote: > > > +1 (binding) > > > > > > On 11/14/19 3:48 PM, Guozhang Wang wrote: > > > +1 (binding), thanks for the KIP! > > > > > >

Re: Potential Bug in 2.3 version (leading to deletion of state directories)

Hi Navinder and Giridhar, Thanks for the clarification. I think the motivation is reasonable. Although, I'm still a little unsure how this condition occurs. In addition to what I mentioned before, I'd forgotten one other important detail, that the "cleaner thread" should only run when the

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hello, Just fyi, PR was updated and now it incorporates the latest suggestions about joins. `CopartitionedTopicsEnforcer` will throw an exception if number of partitions aren’t the same when using `repartition` operation along with `join`. For more details please take a look at the PR:

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

+1 (binding) On Fri, Nov 15, 2019 at 1:11 AM Matthias J. Sax wrote: > +1 (binding) > > > On 11/14/19 3:48 PM, Guozhang Wang wrote: > > +1 (binding), thanks for the KIP! > > > > Guozhang > > > > On Fri, Nov 15, 2019 at 4:38 AM Navinder Brar > > wrote: > > > >> Hello all, > >> > >> I'd like to

Re: KafkaChangeLog Segment Bytes Kafka version Error V2.0.0

@hello any one for this bug ? On 2019/11/12 14:08:15, Elmahdi FRID wrote: > hello Folks > > I create new topic with params > > Topic:testKafkachangelog PartitionCount:3ReplicationFactor:3 > Configs:segment.bytes=5000,retention.ms=60,cleanup.policy=compact >

[jira] [Created] (KAFKA-9195) Use Randomized State Directory Names in Streams System Tests

Bruno Cadonna created KAFKA-9195: Summary: Use Randomized State Directory Names in Streams System Tests Key: KAFKA-9195 URL: https://issues.apache.org/jira/browse/KAFKA-9195 Project: Kafka

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

See Changes: [bbejeck] KAFKA-9011: Removed multiple calls to supplier.get() in order to avoid -- [...truncated 5.58 MB...] org.apache.kafka.streams.TestTopicsTest >

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Thanks a lot for the input Sophie. Your example is quite useful, and I would use it to support my claim that a "partition hint" for `Grouped` seems "useless" and does not improve the user experience. 1) You argue that a new user would be worries about repartitions topics with too many paritions.