[jira] [Commented] (KAFKA-2421) Upgrade LZ4 to version 1.3 to avoid crashing with IBM Java 7

[ https://issues.apache.org/jira/browse/KAFKA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734674#comment-14734674 ] Rajini Sivaram commented on KAFKA-2421: --- [~junrao] Sorry I was away for the last couple of weeks.

[jira] [Commented] (KAFKA-2421) Upgrade LZ4 to version 1.3 to avoid crashing with IBM Java 7

[ https://issues.apache.org/jira/browse/KAFKA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734672#comment-14734672 ] Rajini Sivaram commented on KAFKA-2421: --- Updated reviewboard

[jira] [Updated] (KAFKA-2421) Upgrade LZ4 to version 1.3 to avoid crashing with IBM Java 7

[ https://issues.apache.org/jira/browse/KAFKA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2421: -- Attachment: kafka-2421_2015-09-08_11:38:03.patch > Upgrade LZ4 to version 1.3 to avoid crashing

Re: Review Request 37357: Patch for KAFKA-2421: Upgrade to LZ4 version 1.3 and update reference to Utils method that was moved to SafeUtils

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37357/ --- (Updated Sept. 8, 2015, 11:38 a.m.) Review request for kafka. Summary

[jira] [Commented] (KAFKA-2417) Ducktape tests for SSL/TLS

[ https://issues.apache.org/jira/browse/KAFKA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734719#comment-14734719 ] Rajini Sivaram commented on KAFKA-2417: --- [~granders] Are you working on this task? I would be happy

[jira] [Commented] (KAFKA-2417) Ducktape tests for SSL/TLS

[ https://issues.apache.org/jira/browse/KAFKA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734728#comment-14734728 ] Ismael Juma commented on KAFKA-2417: Regarding running the existing tests with SSL enabled, yes that

Re: Maybe 0.8.3 should really be 0.9.0?

I propose a simple rename: s/0.8.3/0.9.0/ No change of scope and not including current 0.9.0 issues. On Tue, Sep 8, 2015 at 11:36 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Is the plan to release 0.9 in October with the features currently targeted > for 0.8.3, or would 0.9 be a

Re: Maybe 0.8.3 should really be 0.9.0?

+1 on 0.9.0 On Tue, Sep 8, 2015 at 4:07 PM, Ashish Singh wrote: > +1 on 0.9.0 > > On Tue, Sep 8, 2015 at 12:00 PM, Gwen Shapira wrote: > > > I propose a simple rename: s/0.8.3/0.9.0/ > > > > No change of scope and not including current 0.9.0 issues. > >

Re: Maybe 0.8.3 should really be 0.9.0?

+1 on 0.9.0 On Tue, Sep 8, 2015 at 12:00 PM, Gwen Shapira wrote: > I propose a simple rename: s/0.8.3/0.9.0/ > > No change of scope and not including current 0.9.0 issues. > > On Tue, Sep 8, 2015 at 11:36 AM, Rajini Sivaram < > rajinisiva...@googlemail.com> wrote: > > > Is

Re: Maybe 0.8.3 should really be 0.9.0?

Based on the scope, prefer 0.9. On Tue, Sep 8, 2015 at 11:21 AM, Jay Kreps wrote: > +1 on 0.9 > > -Jay > > On Tue, Sep 8, 2015 at 10:19 AM, Gwen Shapira wrote: > > > Hi Kafka Fans, > > > > What do you think of making the next release (the one with

New consumer subscribe then seek

I have been experimenting with the KafkaConsumer currently in development [1]. Sorry if this should be a question for the user list, but I am not sure if what I am seeing is something not working yet or if I am misunderstanding the API. If I use KafkaConsumer#subscribe to subscribe to a topic

[jira] [Commented] (KAFKA-2517) Performance Regression post SSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735738#comment-14735738 ] Ben Stopford commented on KAFKA-2517: - Yes - what Ismael said. I'll take a look at getting a PR out

Re: Maybe 0.8.3 should really be 0.9.0?

+1 on 0.9 - we may want to adjust our ApiVersions accordingly (i.e., 0.8.3 -> 0.9.0) On Tue, Sep 8, 2015 at 2:02 PM, Guozhang Wang wrote: > +1 on 0.9 as well. > > On Tue, Sep 8, 2015 at 1:32 PM, Aditya Auradkar < > aaurad...@linkedin.com.invalid> wrote: > >> +1 on 0.9 >> >>

Re: Maybe 0.8.3 should really be 0.9.0?

+1 (non-binding) for 0.9. Ismael On Tue, Sep 8, 2015 at 10:19 AM, Gwen Shapira wrote: > Hi Kafka Fans, > > What do you think of making the next release (the one with security, new > consumer, quotas, etc) a 0.9.0 instead of 0.8.3? > > It has lots of new features, and new

[GitHub] kafka pull request: Small change to API doc for seekToEnd() to cla...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/199 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Maybe 0.8.3 should really be 0.9.0?

+1 on 0.9 as well. On Tue, Sep 8, 2015 at 1:32 PM, Aditya Auradkar < aaurad...@linkedin.com.invalid> wrote: > +1 on 0.9 > > On Tue, Sep 8, 2015 at 12:29 PM, Edward Ribeiro > wrote: > > > +1 on 0.9.0 > > > > On Tue, Sep 8, 2015 at 4:07 PM, Ashish Singh

Re: Maybe 0.8.3 should really be 0.9.0?

+1 for 0.9 - we may want to get rid of deprecated configs if possible in this, instead of waiting for 1.0. Thanks, Mayuresh On Tue, Sep 8, 2015 at 2:07 PM, Joel Koshy wrote: > +1 on 0.9 - we may want to adjust our ApiVersions accordingly (i.e., > 0.8.3 -> 0.9.0) > > > On

[jira] [Commented] (KAFKA-2517) Performance Regression post SSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735711#comment-14735711 ] Ismael Juma commented on KAFKA-2517: Implementing `SelChImpl` is undesirable as it's an internal

[jira] [Commented] (KAFKA-2500) Make logEndOffset available in the 0.8.3 Consumer

[ https://issues.apache.org/jira/browse/KAFKA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735694#comment-14735694 ] Will Funnell commented on KAFKA-2500: - [~hachikuji] thanks for looking into this. I'll try and clarify

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/158 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

[ https://issues.apache.org/jira/browse/KAFKA-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735725#comment-14735725 ] ASF GitHub Bot commented on KAFKA-2453: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: 0.8.2

Github user leoricxu closed the pull request at: https://github.com/apache/kafka/pull/198 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Contributor List

Thanks! Added you as well. On Mon, Sep 7, 2015 at 10:11 PM, Prabhjot Bharaj wrote: > My username: pbharaj > > Thanks, > Prabhjot > On Sep 8, 2015 10:14 AM, "Prabhjot Bharaj" wrote: > > > Hi, > > > > Request you to add me as well for code

Re: Contributor List

What's your apache jira user name? On Sep 7, 2015 9:44 PM, "Prabhjot Bharaj" wrote: > Hi, > > Request you to add me as well for code contributions > > Regards, > Prabhjot > On Sep 8, 2015 2:10 AM, "Gwen Shapira" wrote: > > > Done :) > > > > Happy

[jira] [Commented] (KAFKA-1070) Auto-assign node id

[ https://issues.apache.org/jira/browse/KAFKA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734916#comment-14734916 ] Sriharsha Chintalapani commented on KAFKA-1070: --- [~amuraru] I am not sure where you are

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734928#comment-14734928 ] Håkon Hitland commented on KAFKA-2477: -- I was able to enable trace logging on a production server,

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734905#comment-14734905 ] Rajini Sivaram commented on KAFKA-1686: --- The current implementation uses GSSAPI as the only

[jira] [Updated] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Håkon Hitland updated KAFKA-2477: - Attachment: kafka_log_trace.txt Attached trace log from leader. Filtered to only lines for the

[jira] [Commented] (KAFKA-2489) System tests: update benchmark tests to run with new and old consumer

[ https://issues.apache.org/jira/browse/KAFKA-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735924#comment-14735924 ] ASF GitHub Bot commented on KAFKA-2489: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: KAFKA-2489: add benchmark for new consumer

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/179 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (KAFKA-2527) System Test for Quotas in Ducktape

Dong Lin created KAFKA-2527: --- Summary: System Test for Quotas in Ducktape Key: KAFKA-2527 URL: https://issues.apache.org/jira/browse/KAFKA-2527 Project: Kafka Issue Type: Test

[jira] [Created] (KAFKA-2528) Quota Performance Evaluation

Dong Lin created KAFKA-2528: --- Summary: Quota Performance Evaluation Key: KAFKA-2528 URL: https://issues.apache.org/jira/browse/KAFKA-2528 Project: Kafka Issue Type: Sub-task Reporter:

[jira] [Updated] (KAFKA-2527) System Test for Quotas in Ducktape

[ https://issues.apache.org/jira/browse/KAFKA-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2527: Issue Type: Sub-task (was: Test) Parent: KAFKA-2083 > System Test for Quotas in Ducktape >

Re: New consumer subscribe then seek

Hey Phil, You've stumbled onto one of the tricky aspects of the new consumer that we've been talking about recently. KafkaConsumer.subscribe() is asynchronous in the sense that it will return before partitions have been assigned. We could make it synchronous, but we wouldn't be able to guarantee

[jira] [Commented] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735899#comment-14735899 ] Mayuresh Gharat commented on KAFKA-2120: Hi [~junrao], I have uploaded a new patch addressing the

[jira] [Work started] (KAFKA-2527) System Test for Quotas in Ducktape

[ https://issues.apache.org/jira/browse/KAFKA-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2527 started by Dong Lin. --- > System Test for Quotas in Ducktape > -- > >

Jenkins build is back to normal : Kafka-trunk #618

See

Re: New consumer subscribe then seek

On 9/8/15 6:58 PM, Jason Gustafson wrote: > Hey Phil, > > You've stumbled onto one of the tricky aspects of the new consumer that > we've been talking about recently. KafkaConsumer.subscribe() is > asynchronous in the sense that it will return before partitions have been > assigned. We could make

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734918#comment-14734918 ] Sriharsha Chintalapani commented on KAFKA-1686: --- [~rsivaram] Yes I'll make it as

[jira] [Commented] (KAFKA-1070) Auto-assign node id

[ https://issues.apache.org/jira/browse/KAFKA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734938#comment-14734938 ] Adrian Muraru commented on KAFKA-1070: -- [~harsha_ch] I see KAFKA-1973 already fixed that, nw :) >

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735015#comment-14735015 ] Jiangjie Qin commented on KAFKA-2477: - [~hakon] Yes, that's correct. The log appending does the

Re: Maybe 0.8.3 should really be 0.9.0?

Hi Gwen, I certainly think 0.9.0 is better than 0.8.3. As regards semantic versioning, do we have a plan for a 1.0 release? IIUC, compatibility rules don't really apply for pre-1.0 stuff. I'd argue that Kafka already qualifies for 1.x. Aditya On Tue, Sep 8, 2015 at 10:26 AM, Gwen Shapira

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735152#comment-14735152 ] Jiangjie Qin commented on KAFKA-2477: - No worries. I can do that :) > Replicas spuriously deleting

[jira] [Updated] (KAFKA-2517) Performance Regression post SSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-2517: - Priority: Blocker (was: Critical) > Performance Regression post SSL implementation >

Maybe 0.8.3 should really be 0.9.0?

Hi Kafka Fans, What do you think of making the next release (the one with security, new consumer, quotas, etc) a 0.9.0 instead of 0.8.3? It has lots of new features, and new consumer was pretty much scoped for 0.9.0, so it matches our original roadmap. I feel that so many awesome features

Re: Maybe 0.8.3 should really be 0.9.0?

Hi Gwen, What's the expected meaning of the individual digits of the version for this community? Could you give me some insight here? -Flavio > On 08 Sep 2015, at 18:19, Gwen Shapira wrote: > > Hi Kafka Fans, > > What do you think of making the next release (the one with

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14735134#comment-14735134 ] Håkon Hitland commented on KAFKA-2477: -- I don't think I can provide a patch at the moment, I would

[jira] [Assigned] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-2477: --- Assignee: Jiangjie Qin > Replicas spuriously deleting all segments in partition >

Re: [DISCUSS] KIP-31 - Message format change proposal

Hey Todd, Yeah, totally agree the use case is important. I think there are potentially also other uses that having access by time opens up too. -Jay On Sun, Sep 6, 2015 at 9:54 PM, Todd Palino wrote: > So, with regards to why you want to search by timestamp, the biggest >

Re: Maybe 0.8.3 should really be 0.9.0?

We've been rather messy about this in the past, but I'm hoping to converge toward semantic versioning: http://semver.org/ 0.9.0 will fit since we are adding new functionality in backward compatible manner. On Tue, Sep 8, 2015 at 10:23 AM, Flavio Junqueira wrote: > Hi Gwen, > >

Re: [DISCUSS] KIP-31 - Message format change proposal

Hey Beckett, I was proposing splitting up the KIP just for simplicity of discussion. You can still implement them in one patch. I think otherwise it will be hard to discuss/vote on them since if you like the offset proposal but not the time proposal what do you do? Introducing a second notion of

Re: Maybe 0.8.3 should really be 0.9.0?

I don't know of any 1.0 plans. IMO, it makes sense to have 0.9.0 out first, and then discuss what it will take to get to 1.0. Does that make sense? On Tue, Sep 8, 2015 at 10:39 AM, Aditya Auradkar < aaurad...@linkedin.com.invalid> wrote: > Hi Gwen, > > I certainly think 0.9.0 is better than

Re: Maybe 0.8.3 should really be 0.9.0?

Based on the new feature in next release, 0.9 looks reasonable. There might be some other things worth thinking about. Although we have a lot of new feature added, many of them are actually either still in development or not well tested yet. For example, for security features, only SSL is done

Re: Maybe 0.8.3 should really be 0.9.0?

+1 for 0.9. Thanks, Jun On Tue, Sep 8, 2015 at 3:04 PM, Ismael Juma wrote: > +1 (non-binding) for 0.9. > > Ismael > > On Tue, Sep 8, 2015 at 10:19 AM, Gwen Shapira wrote: > > > Hi Kafka Fans, > > > > What do you think of making the next release (the one

Re: Review Request 36858: Patch for KAFKA-2120

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36858/#review98136 --- Thanks for the patch. A few more minor comments below.