Build failed in Jenkins: kafka-0.11.0-jdk7 #391

See Changes: [github] MINOR: fix Streams quickstart (#5331) -- [...truncated 213.81 KB...] kafka.producer.AsyncProducerTest > testFailedSendRetryLogic PASSED

Re: [VOTE] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

Hi, I don't seem to find response to John's comment : http://search-hadoop.com/m/Kafka/uyzND11alrn1G5N3Y1?subj=Re+Discuss+KIP+321+Add+method+to+get+TopicNameExtractor+in+TopologyDescription On Tue, Jul 3, 2018 at 7:38 PM, Nishanth Pradeep wrote: > Hello, > > I would like to start the vote on

Re: [VOTE] 2.0.0 RC1

+1 tentative rolling upgrade of tiny shared staging multitenacy (200+ consumer groups) cluster from 1.1 to 2.0.0-rc1. cluster looks healthy. Will monitor. On Tue, Jul 3, 2018 at 8:18 AM Harsha wrote: > +1. > > 1) Ran unit tests > 2) 3 node cluster , tested basic operations. > > Thanks, > Harsha

[VOTE] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

Hello, I would like to start the vote on extending the TopologyDescription.Sink interface to return the class of the TopicNameExtractor in cases where dynamic routing is used. The user can override the toString method of the TopicNameExtractor class in order to provide a better textual

Build failed in Jenkins: kafka-0.11.0-jdk7 #390

See Changes: [github] MINOR: updatd for 0.11.0.3 release (#5326) -- [...truncated 1.56 MB...] org.apache.kafka.streams.kstream.internals.KTableAggregateTest >

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hey Jun, Thanks much for the comments. It is good point. So the feature may be useful for JBOD use-case. I have one question below. Hey Lucas, Do you think this feature is also useful for non-JBOD setup or it is only useful for the JBOD setup? It may be useful to understand this. When the

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

For #1, I agree that obtaining good default is not trivial. We can revisit in the future. For #2, the table is readable. Thanks On Tue, Jul 3, 2018 at 4:23 PM, Lucas Wang wrote: > @Ted > For #1, it's probably hard to predict M since it also depends on the > hardware. > I'm not sure how to use

Build failed in Jenkins: kafka-0.10.2-jdk7 #224

See Changes: [jason] MINOR: Fix race condition in TestVerifiableProducer sanity test [jason] MINOR: Fix kafkatest snapshot version for 0.10.2.3 [github] MINOR: update for 0.10.2.2 release (#5327)

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Thanks for the insightful comment, Jun. @Dong, Since both of the two comments in your previous email are about the benefits of this KIP and whether it's useful, in light of Jun's last comment, do you agree that this KIP can be beneficial in the case mentioned by Jun? Please let me know, thanks!

[jira] [Created] (KAFKA-7131) Update release script to generate announcement email text

Matthias J. Sax created KAFKA-7131: -- Summary: Update release script to generate announcement email text Key: KAFKA-7131 URL: https://issues.apache.org/jira/browse/KAFKA-7131 Project: Kafka

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

@Ted For #1, it's probably hard to predict M since it also depends on the hardware. I'm not sure how to use the suggested formula for the default value if we don't know M. Also TO is the default timeout we want to figure out, and the formula seems to be recursive. I'd suggest we stay with the

Re: [DISCUSS] KIP-320: Allow fetchers to detect and handle log truncation

Hey Jason, Thanks much for your thoughtful explanation. Yes the solution using findOffsets(offset, leaderEpoch) also works. The advantage of this solution it adds only one API instead of two APIs. The concern is that its usage seems a bit more clumsy for advanced users. More specifically,

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

See

Build failed in Jenkins: kafka-0.11.0-jdk7 #389

See Changes: [jason] MINOR: Fix kafkatest snapshot version for 0.11.0.4 -- [...truncated 1.56 MB...] org.apache.kafka.streams.kstream.internals.KStreamImplTest >

Re: [VOTE] KIP-280: Enhanced log compaction

Hi, Luis, Thanks for the KIP. Overall, this seems a useful KIP. A few comments below. 1. I guess both new configurations will be at the topic level? 2. Since the log cleaner now needs to keep both the offset and another long (say timestamp) in the de-dup map, it reduces the number of keys that

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

+1. Thanks, Harsha On Tue, Jul 3rd, 2018 at 9:22 AM, Ted Yu wrote: > > > > +1 > > On Tue, Jul 3, 2018 at 9:05 AM, Mickael Maison < mickael.mai...@gmail.com > > > wrote: > > > +1 (non binding) > > Thanks for the KIP > > > > On Tue, Jul 3, 2018 at 4:59 PM, Vahid S Hashemian > > <

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

See Changes: [rajinisivaram] MINOR: Include quota related interfaces to javadocs (#5325) -- [...truncated 869.07 KB...] kafka.admin.ResetConsumerGroupOffsetTest >

Re: [VOTE] KIP-280: Enhanced log compaction

Sorry to join the discussion late. Can you you add to the motivation the use cases for header-based compaction. This seems not very clear to me. Thanks, Jason On Mon, Jul 2, 2018 at 11:00 AM, Guozhang Wang wrote: > Hi Luis, > > I believe that compaction property is indeed overridable at

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

Awesome. Thanks Matthias! On Tue, Jul 3, 2018 at 12:44 PM, Yishun Guan wrote: > Nice! Thanks~ > > On Tue, Jul 3, 2018, 12:16 PM Ismael Juma wrote: > > > Thanks Matthias! > > > > On Tue, 3 Jul 2018, 11:31 Matthias J. Sax, wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA512 >

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hi, Lucas, Dong, If all disks on a broker are slow, one probably should just kill the broker. In that case, this KIP may not help. If only one of the disks on a broker is slow, one may want to fail that disk and move the leaders on that disk to other brokers. In that case, being able to process

[jira] [Resolved] (KAFKA-2933) Failure in kafka.api.PlaintextConsumerTest.testMultiConsumerDefaultAssignment

[ https://issues.apache.org/jira/browse/KAFKA-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-2933. Resolution: Cannot Reproduce It's been a long time since we've seen this, so I will close.

Build failed in Jenkins: kafka-trunk-jdk10 #275

See Changes: [rajinisivaram] MINOR: Include quota related interfaces to javadocs (#5325) -- [...truncated 1.98 MB...] org.apache.kafka.streams.StreamsConfigTest >

[ANNOUNCE] Apache Kafka 0.10.2.2 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The Apache Kafka community is pleased to announce the release for Apache Kafka 0.10.2.2. This is a bug fix release and it includes fixes and improvements from 29 JIRAs, including a few critical bugs. All of the changes in this release can be

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

Nice! Thanks~ On Tue, Jul 3, 2018, 12:16 PM Ismael Juma wrote: > Thanks Matthias! > > On Tue, 3 Jul 2018, 11:31 Matthias J. Sax, wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > The Apache Kafka community is pleased to announce the release for > > Apache Kafka 0.11.0.3.

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

Thanks Matthias! On Tue, 3 Jul 2018, 11:31 Matthias J. Sax, wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > The Apache Kafka community is pleased to announce the release for > Apache Kafka 0.11.0.3. > > > This is a bug fix release and it includes fixes and improvements from > 27

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

Thanks Matthias for driving the release! On Tue, Jul 3, 2018 at 11:31 AM, Matthias J. Sax wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > The Apache Kafka community is pleased to announce the release for > Apache Kafka 0.11.0.3. > > > This is a bug fix release and it includes

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

See Changes: [wangguoz] MINOR: Fix standby streamTime (#5288) -- [...truncated 871.08 KB...] kafka.security.auth.ResourceTest > shouldParseThreePartWithEmbeddedSeparators

[ANNOUNCE] Apache Kafka 0.11.0.3 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The Apache Kafka community is pleased to announce the release for Apache Kafka 0.11.0.3. This is a bug fix release and it includes fixes and improvements from 27 JIRAs, including a few critical bugs. All of the changes in this release can be

Re: [DISCUSS] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

Hi again, Chia-Ping, Thanks! I took a look at it, and it seems like a good change to me. I don't know if it will generate much discussion, so I recommend just letting it steep for another day or two and then moving on to a vote if no one else chimes in. Just really scraping my mind for concerns

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

Hi Flávio, Thanks! I think that we can actually do this, but the API could be better. I've included Java code below, but I'll copy and modify your example so we're on the same page. EXERCISE 1: - The case is "total counting of events for a huge website" - Tasks from Application A will have

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

+1 On Tue, Jul 3, 2018 at 9:05 AM, Mickael Maison wrote: > +1 (non binding) > Thanks for the KIP > > On Tue, Jul 3, 2018 at 4:59 PM, Vahid S Hashemian > wrote: > > +1 (non-binding) > > > > --Vahid > > > > > > > > From: Gwen Shapira > > To: dev > > Date: 07/03/2018 08:49 AM > >

Re: [DISCUSS] KIP-325: Extend Consumer Group Command to Show Beginning Offsets

Hi Jason, Thanks for the feedback. Your suggestions make sense to me. I think I'm more in favor of adding this info to kafka-topic tool (through another KIP) since it is not consumer group specific. I'll wait for Gwen and others to comment before making changes to the KIP. --Vahid From:

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

+1 (non binding) Thanks for the KIP On Tue, Jul 3, 2018 at 4:59 PM, Vahid S Hashemian wrote: > +1 (non-binding) > > --Vahid > > > > From: Gwen Shapira > To: dev > Date: 07/03/2018 08:49 AM > Subject:Re: [VOTE] KIP-322: Return new error code for DeleteTopics > API when topic

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

+1 (non-binding) --Vahid From: Gwen Shapira To: dev Date: 07/03/2018 08:49 AM Subject:Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled. +1 On Tue, Jul 3, 2018 at 8:24 AM, Manikumar wrote: > Manikumar > Fri, Jun 29, 7:59 PM

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

Hi Matthias, +1 (binding) Thank you for running the release. Ran quick start with binary, tests with source, checked javadocs. Regards, Rajini On Mon, Jul 2, 2018 at 9:34 PM, Harsha wrote: > +1. > > 1) Ran unit tests > 2) 3 node cluster , tested basic operations. > > Thanks, > Harsha > >

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

+1 On Tue, Jul 3, 2018 at 8:24 AM, Manikumar wrote: > Manikumar > Fri, Jun 29, 7:59 PM (4 days ago) > to dev > Hi All, > > I would like to start voting on KIP-322 which would return new error code > for DeleteTopics API when topic deletion disabled. > >

[VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

Manikumar Fri, Jun 29, 7:59 PM (4 days ago) to dev Hi All, I would like to start voting on KIP-322 which would return new error code for DeleteTopics API when topic deletion disabled. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=87295558 Thanks,

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

Great feature you have there! I'll try to exercise here how we would achieve the same functional objectives using your KIP: EXERCISE 1: - The case is "total counting of events for a huge website" - Tasks from Application A will have something like: .stream(/site-events)

Re: [DISCUSS] KIP-328: Ability to suppress updates for KTables

Hi Guozhang, I see. It seems like if we want to decouple 1) and 2), we need to alter the definition of the window. Do you think it would close the gap if we added a "window close" time to the window definition? Such as: builder.stream("input") .groupByKey() .windowedBy( TimeWindows

[jira] [Created] (KAFKA-7130) EOFException after rolling log segment

Karsten Schnitter created KAFKA-7130: Summary: EOFException after rolling log segment Key: KAFKA-7130 URL: https://issues.apache.org/jira/browse/KAFKA-7130 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-7129) Dynamic default value for number of thread configuration

Damien Gasparina created KAFKA-7129: --- Summary: Dynamic default value for number of thread configuration Key: KAFKA-7129 URL: https://issues.apache.org/jira/browse/KAFKA-7129 Project: Kafka