[jira] [Resolved] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

2018-03-05 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3806. Resolution: Fixed Assignee: Ewen Cheslack-Postava > Adjust default values of log.reten

[jira] [Resolved] (KAFKA-5471) Original Kafka paper link broken

2018-03-05 Thread Ewen Cheslack-Postava (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5471. -- Resolution: Fixed Assignee: Ewen Cheslack-Postava Updated the link to what

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

2018-03-05 Thread Apache Jenkins Server
See

[jira] [Created] (KAFKA-6613) The controller shouldn't stop partition reassignment after an exception is being thrown

2018-03-05 Thread chandra kasiraju (JIRA)
chandra kasiraju created KAFKA-6613: --- Summary: The controller shouldn't stop partition reassignment after an exception is being thrown Key: KAFKA-6613 URL: https://issues.apache.org/jira/browse/KAFKA-6613

[jira] [Resolved] (KAFKA-6610) initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset"

2018-03-05 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6610. Resolution: Duplicate Thanks for the report. This looks like KAFKA-3978. We are still not su

答复: [VOTE] KIP-265: Make Windowed Serde to public APIs

2018-03-05 Thread Hu Xi
+1 (non-binding) 发件人: Matthias J. Sax 发送时间: 2018年3月6日 8:19 收件人: dev@kafka.apache.org 主题: Re: [VOTE] KIP-265: Make Windowed Serde to public APIs +1 (binding) Thanks for the KIP Guozhang! -Matthias On 3/5/18 2:41 PM, Bill Bejeck wrote: > Thanks for the KIP Guozh

Re: [VOTE] KIP-265: Make Windowed Serde to public APIs

2018-03-05 Thread Matthias J. Sax
+1 (binding) Thanks for the KIP Guozhang! -Matthias On 3/5/18 2:41 PM, Bill Bejeck wrote: > Thanks for the KIP Guozhang. > > +1 > > -Bill > > On Mon, Mar 5, 2018 at 5:11 PM, Ted Yu wrote: > >> +1 >> >> On Mon, Mar 5, 2018 at 1:46 PM, Guozhang Wang wrote: >> >>> Hello all, >>> >>> I'd like

[jira] [Created] (KAFKA-6612) Added logic to prevent increasing partition counts during topic deletion

2018-03-05 Thread Lucas Wang (JIRA)
Lucas Wang created KAFKA-6612: - Summary: Added logic to prevent increasing partition counts during topic deletion Key: KAFKA-6612 URL: https://issues.apache.org/jira/browse/KAFKA-6612 Project: Kafka

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

2018-03-05 Thread Jason Gustafson
Hey Vahid, On point #1 below: since the expiration timer starts ticking after the > group becomes Empty the expire_timestamp of group offsets will be set when > that transition occurs. In normal cases that expire_timestamp is > calculated as "current timestamp" + "broker's offset retention". Then

[jira] [Created] (KAFKA-6611) Re-write simple benchmark in system tests with JMXTool

2018-03-05 Thread Guozhang Wang (JIRA)
Guozhang Wang created KAFKA-6611: Summary: Re-write simple benchmark in system tests with JMXTool Key: KAFKA-6611 URL: https://issues.apache.org/jira/browse/KAFKA-6611 Project: Kafka Issue Ty

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

2018-03-05 Thread Jason Gustafson
@Guozhang I probably have suggested all options at some point or another, including most recently, the current KIP! I was thinking that practically speaking, the request timeout defines how long the user is willing to wait for a response. The consumer doesn't really have a complex send process like

Re: [VOTE] KIP-265: Make Windowed Serde to public APIs

2018-03-05 Thread Bill Bejeck
Thanks for the KIP Guozhang. +1 -Bill On Mon, Mar 5, 2018 at 5:11 PM, Ted Yu wrote: > +1 > > On Mon, Mar 5, 2018 at 1:46 PM, Guozhang Wang wrote: > > > Hello all, > > > > I'd like to start voting on KIP-265, on making windowed serde to public > > APIs of Kafka Streams. It involves a couple of

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

2018-03-05 Thread Apache Jenkins Server
See Changes: [github] KAFKA-6054: Code cleanup to prepare the actual fix for an upgrade path [mjsax] MINOR: Add System test for standby task-rebalancing (#4554) -- [...tr

Re: [VOTE] KIP-265: Make Windowed Serde to public APIs

2018-03-05 Thread Ted Yu
+1 On Mon, Mar 5, 2018 at 1:46 PM, Guozhang Wang wrote: > Hello all, > > I'd like to start voting on KIP-265, on making windowed serde to public > APIs of Kafka Streams. It involves a couple of new configs, plus a few new > public classes for windowed serializer and deserializer, and also adding

[VOTE] KIP-265: Make Windowed Serde to public APIs

2018-03-05 Thread Guozhang Wang
Hello all, I'd like to start voting on KIP-265, on making windowed serde to public APIs of Kafka Streams. It involves a couple of new configs, plus a few new public classes for windowed serializer and deserializer, and also adding the corresponding console consumer options in order to fetch from a

Re: [VOTE] KIP-186: Increase offsets retention default to 7 days

2018-03-05 Thread Ismael Juma
+1 (binding) Ismael On Mon, Mar 5, 2018 at 11:35 AM, Ewen Cheslack-Postava wrote: > I'd like to kick off voting for KIP-186: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 186%3A+Increase+offsets+retention+default+to+7+days > > This is the trivial fix that people in the DISCUSS thre

[VOTE] KIP-186: Increase offsets retention default to 7 days

2018-03-05 Thread Ewen Cheslack-Postava
I'd like to kick off voting for KIP-186: https://cwiki.apache.org/confluence/display/KAFKA/KIP-186%3A+Increase+offsets+retention+default+to+7+days This is the trivial fix that people in the DISCUSS thread were in favor of. There are some ideas for further refinements, but I think we can follow up

Re: [DISCUSS] KIP-186: Increase offsets retention default to 7 days

2018-03-05 Thread Ewen Cheslack-Postava
Reviving this thread. @Stevo I think there are more refinements we can make, but I'd like to get at least this pushed through because this keeps biting people unexpectedly. How about we bump the default now just to address the immediate issue and we can follow up with additional refinements in fut

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

2018-03-05 Thread Jason Gustafson
Great discussion. I think I'm wondering whether we can continue to leave Kafka agnostic to the partitioning strategy. The challenge is communicating the partitioning logic from producers to consumers so that the dependencies between each epoch can be determined. For the sake of discussion, imagine

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

2018-03-05 Thread Matthias J. Sax
Thanks for clarification Colin! I like the proposal. -Matthias On 3/3/18 2:53 PM, Colin McCabe wrote: > I agree. --execute is inconsistent with the way UNIX commands normally work. > Normally, if you don't want something to be executed, you pass something like > a --dry-run flag. Users expe

[jira] [Created] (KAFKA-6610) initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset"

2018-03-05 Thread dongyan li (JIRA)
dongyan li created KAFKA-6610: - Summary: initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset" Key: KAFKA-6610 URL: https://issues.apache.org/jira/browse/KAFKA-6610

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

2018-03-05 Thread Jan Filipiak
Hi Dong thank you very much for your questions. regarding the time spend copying data across: It is correct that copying data from a topic with one partition mapping to a topic with a different partition mapping takes way longer than we can stop producers. Tens of minutes is a very optimistic