[jira] [Updated] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3123: --- Fix Version/s: 0.10.0.0 > Follower Broker cannot start if offsets are already out of range >

[jira] [Commented] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184614#comment-15184614 ] ASF GitHub Bot commented on KAFKA-3123: --- GitHub user soumyajit-sahu opened a pull request:

[GitHub] kafka pull request: KAFKA-3123: Follower Broker cannot start if of...

GitHub user soumyajit-sahu opened a pull request: https://github.com/apache/kafka/pull/1028 KAFKA-3123: Follower Broker cannot start if offsets are already out of range Function abortAndPauseCleaning() doesn't have to throw exception if the state is already LogCleaningAborted or

[jira] [Commented] (KAFKA-2982) Mark the old Scala producer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184612#comment-15184612 ] Ismael Juma commented on KAFKA-2982: The vote has passed so we should do this for 0.10.0.0.

Re: [VOTE] Deprecating the old Scala producers for 0.10.0.0

Thanks everyone for voting. +1 from me too. The vote passed with 6 binding +1s (Neha, Joe, Gwen, Guozhang, Joel, Ewen) and 4 non-binding +1s (Becket, Ashish, Grant and me). The discussion will now move to KAFKA-2982. Ismael On Mon, Mar 7, 2016 at 7:12 PM, Ewen Cheslack-Postava

[jira] [Updated] (KAFKA-3201) Add system test for KIP-31 and KIP-32 - Upgrade Test

[ https://issues.apache.org/jira/browse/KAFKA-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3201: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[jira] [Commented] (KAFKA-3201) Add system test for KIP-31 and KIP-32 - Upgrade Test

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

[GitHub] kafka pull request: KAFKA-3201: Added rolling upgrade system tests...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/980 --- 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] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3047: --- Fix Version/s: 0.8.1.2 > Explicit offset assignment in Log.append can corrupt the log >

[jira] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3047: --- Fix Version/s: (was: 0.8.1.2) 0.10.0.0 > Explicit offset assignment in

[jira] [Assigned] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3047: -- Assignee: Ismael Juma (was: Jay Kreps) > Explicit offset assignment in Log.append can corrupt

[jira] [Commented] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184535#comment-15184535 ] chen zhu commented on KAFKA-3261: - [~guozhang] I am sorry for the late reply. Are you suggesting to

[jira] [Commented] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184516#comment-15184516 ] chen zhu commented on KAFKA-3261: - [~ijuma] yes, that can be done. But if we use the same regrex(in this

Re: [VOTE] Release plan - Kafka 0.10.0

+1 Thanks, Harsha On Mon, Mar 7, 2016, at 09:49 PM, Jun Rao wrote: > +1 > > Thanks, > > Jun > > On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > > > Greetings Kafka Developer Community, > > > > As you all know, we have few big features that are almost complete > >

Re: [VOTE] Release plan - Kafka 0.10.0

+1 Thanks, Jun On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > Greetings Kafka Developer Community, > > As you all know, we have few big features that are almost complete > (Timestamps! Interceptors! Streams!). It is time to start planning our > next release. > > I

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Makes sense to me. Thanks! On Mon, Mar 7, 2016 at 9:25 PM, Harsha wrote: > It doesn't need any release vehicle but still the work can move forward. > If anyone is interested in the KIP please do the review and provide the > comments. > > -Harsha > > On Mon, Mar 7, 2016, at 04:59

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

It doesn't need any release vehicle but still the work can move forward. If anyone is interested in the KIP please do the review and provide the comments. -Harsha On Mon, Mar 7, 2016, at 04:59 PM, Ismael Juma wrote: > I agree that it would be good to have more time to review and discuss >

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

See Changes: [cshapi] MINOR: Remove usage of deprecated junit.framework.Assert [cshapi] MINOR: tidy up spacing for ConsumerGroupCommand related to KAFKA-1476 ��� [cshapi] KAFKA-2068; KAFKA-2069; Replace OffsetCommit and OffsetFetch

Jenkins build is back to normal : kafka-trunk-jdk7 #1096

See

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184345#comment-15184345 ] Gwen Shapira commented on KAFKA-2967: - We are using Gradle to package the release, and it also runs

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184283#comment-15184283 ] Christian Posta commented on KAFKA-2967: Many thanks for the review [~gwenshap]!! Let me take a

[jira] [Updated] (KAFKA-2069) Replace OffsetFetch request/response with their org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2069: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

[jira] [Updated] (KAFKA-2068) Replace OffsetCommit Request/Response with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2068: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

[jira] [Commented] (KAFKA-2068) Replace OffsetCommit Request/Response with org.apache.kafka.common.requests equivalent

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

[GitHub] kafka pull request: KAFKA-2068; KAFKA-2069; Replace OffsetCommit a...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/927 --- 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-1476) Get a list of consumer groups

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

[GitHub] kafka pull request: MINOR: tidy up spacing for ConsumerGroupComman...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/945 --- 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

[GitHub] kafka pull request: MINOR: Remove usage of deprecated junit.framew...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/938 --- 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-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184231#comment-15184231 ] Gwen Shapira commented on KAFKA-2967: - Thanks for the work [~ceposta]! Is there any way to integrate

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

Hi Jason, Yes, 0.9 clients should still work with 0.10 brokers. Thanks, Jiangjie (Becket) Qin On Mon, Mar 7, 2016 at 4:10 PM, Jason Gustafson wrote: > +users > > On Mon, Mar 7, 2016 at 4:09 PM, Jason Gustafson > wrote: > > > Hey Ismael, > > > > Thanks

Re: [VOTE] Release plan - Kafka 0.10.0

I added a section on "how to contribute to the release" to the release plan: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 Please help out! :) On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > Greetings Kafka Developer Community, > > As you all

[jira] [Resolved] (KAFKA-3349) Add system tests for upgrade from 0.8.2.x to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh resolved KAFKA-3349. --- Resolution: Duplicate > Add system tests for upgrade from 0.8.2.x to 0.10.0.0 >

[jira] [Resolved] (KAFKA-3348) Add system tests for upgrade from 0.9.0.1 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh resolved KAFKA-3348. --- Resolution: Duplicate > Add system tests for upgrade from 0.9.0.1 to 0.10.0.0 >

Re: [VOTE] Release plan - Kafka 0.10.0

Perfect! Missed out those JIRAs. They should cover the concern. On Mon, Mar 7, 2016 at 5:21 PM, Gwen Shapira wrote: > We are planning on supporting 0.8.2 upgrades too. > > We already have KAFKA-3188 and KAFKA-3201 for the tests. Do you think > they are incomplete? > > On Mon,

[GitHub] kafka pull request: MINOR: add back old constructor of ConsumerRec...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1027 MINOR: add back old constructor of ConsumerRecord You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka consumer-record-constructor

[jira] [Commented] (KAFKA-3348) Add system tests for upgrade from 0.9.0.1 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184161#comment-15184161 ] Ashish K Singh commented on KAFKA-3348: --- Awesome!. We can mark these as duplicate then. > Add

Re: [VOTE] Release plan - Kafka 0.10.0

We are planning on supporting 0.8.2 upgrades too. We already have KAFKA-3188 and KAFKA-3201 for the tests. Do you think they are incomplete? On Mon, Mar 7, 2016 at 5:15 PM, Ashish Singh wrote: > +1 (non-binding) > > My understanding is that we decided to support upgrading

[jira] [Updated] (KAFKA-3348) Add system tests for upgrade from 0.9.0.1 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3348: -- Description: System upgrade tests needs to enhanced to test upgrade from 0.9.0.1 to 0.10.0.0.

[jira] [Updated] (KAFKA-3348) Add system tests for upgrade from 0.9.0.1 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3348: -- Summary: Add system tests for upgrade from 0.9.0.1 to 0.10.0.0 (was: Add system tests for

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Can you explain the process for a adding a new mechanism based on current KIP? My thought is that if it requires modifying Apache Kafka code, it is not pluggable enough. On Mon, Mar 7, 2016 at 4:04 PM, Rajini Sivaram wrote: > Gwen, > > In cases where you want

[jira] [Commented] (KAFKA-3348) Add system tests for upgrade from 0.9.1.0 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184148#comment-15184148 ] Ismael Juma commented on KAFKA-3348: And there's a PR for KAFKA-3201 already too. > Add system tests

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) My understanding is that we decided to support upgrading from 08.2.x to 0.10.0.0 as well, due to short release cycle. Please correct me if that is not true. Created KAFKA-3348 and KAFKA-3349 to add tests for making sure following paths work fine. 1. 0.8.2.x -> 0.10.0.0 2.

[jira] [Commented] (KAFKA-3348) Add system tests for upgrade from 0.9.1.0 to 0.10.0.0

[ https://issues.apache.org/jira/browse/KAFKA-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184141#comment-15184141 ] Gwen Shapira commented on KAFKA-3348: - 1. We also need to test 0.8.X upgrades 2. We already have

[jira] [Commented] (KAFKA-3346) Rename "Mode" to "SslMode"

[ https://issues.apache.org/jira/browse/KAFKA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184139#comment-15184139 ] Gwen Shapira commented on KAFKA-3346: - actually, I like connectionMode better. But I still think that

[jira] [Created] (KAFKA-3349) Add system tests for upgrade from 0.8.2.x to 0.10.0.0

Ashish K Singh created KAFKA-3349: - Summary: Add system tests for upgrade from 0.8.2.x to 0.10.0.0 Key: KAFKA-3349 URL: https://issues.apache.org/jira/browse/KAFKA-3349 Project: Kafka Issue

[jira] [Commented] (KAFKA-3346) Rename "Mode" to "SslMode"

[ https://issues.apache.org/jira/browse/KAFKA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184136#comment-15184136 ] Gwen Shapira commented on KAFKA-3346: - Maybe we can change Mode to loginType and loginType to

[jira] [Created] (KAFKA-3348) Add system tests for upgrade from 0.9.1.0 to 0.10.0.0

Ashish K Singh created KAFKA-3348: - Summary: Add system tests for upgrade from 0.9.1.0 to 0.10.0.0 Key: KAFKA-3348 URL: https://issues.apache.org/jira/browse/KAFKA-3348 Project: Kafka Issue

Re: [DISCUSS] KIP-49: Fair Partition Assignment Strategy

+1 On Mon, Mar 7, 2016 at 4:58 PM, Gwen Shapira wrote: > Hi Team, > > Since there is a fairly busy release coming up in 2 weeks, and since > partition-assignors are pluggable and don't need to be part of an > Apache Kafka release in order to be useful, can we delay this KIP

Re: [VOTE] Release plan - Kafka 0.10.0

Important clarification: In order to keep the release quality up to the usual Kafka standards, we will want to only commit tested features. When deciding on whether to push your feature into 0.10.0 or delay to the next release, please take into account whether you'll have time to complete the

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

I agree that it would be good to have more time to review and discuss KIP-48. Ismael On Tue, Mar 8, 2016 at 12:55 AM, Gwen Shapira wrote: > Hi Team, > > Since KIP-48 depends on KIP-43, which is already a bit of a risk for > the next release - any chance we can delay

Re: [DISCUSS] KIP-49: Fair Partition Assignment Strategy

Hi Team, Since there is a fairly busy release coming up in 2 weeks, and since partition-assignors are pluggable and don't need to be part of an Apache Kafka release in order to be useful, can we delay this KIP to release 0.10.1 or 0.11.0 (whichever is earlier)? This will give the community a

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Hi Team, Since KIP-48 depends on KIP-43, which is already a bit of a risk for the next release - any chance we can delay delegation tokens to Kafka 0.10.1? With the community working on a release every 3 month, this is not a huge delay. Gwen On Fri, Feb 26, 2016 at 5:11 PM, Ashish Singh

Re: [VOTE] Release plan - Kafka 0.10.0

In order to track the many KIPs that we are trying to land in the next two weeks, I created this page: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 There are a lot of KIPs under discussion and not too much time to finalize all of them. Lets do our best to review, discuss

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) BTW, if possible, I would like to have KIP-33 in 0.10.0 to solve the long pending retention issue. On Mon, Mar 7, 2016 at 3:26 PM, Joel Koshy wrote: > +1 > > On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > > > Greetings Kafka

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

+ Parth, Harsha On Mon, Mar 7, 2016 at 4:32 PM, Ashish Singh wrote: > Thanks Gwen. > > @Parth, @Harsha pinging you guys for your feedback. Based on discussion on > JIRA, we have following open questions. > >1. > >How to allow an authorizer implementation to specify

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Thanks Gwen. @Parth, @Harsha pinging you guys for your feedback. Based on discussion on JIRA, we have following open questions. 1. How to allow an authorizer implementation to specify supported principal types? An alternative of providing supported Principal types via interface is

Re: KIP call to discuss some of the outstanding KIPs

Gwen, thanks for the info and the wiki! On Mon, Mar 7, 2016 at 4:23 PM, Gwen Shapira wrote: > Hi, > > Jun is out on a secret mission this week, so we will need to postpone > the meeting to next week. > > Meanwhile, I created a release plan page with our favorite KIPs, to >

Re: KIP call to discuss some of the outstanding KIPs

Hi, Jun is out on a secret mission this week, so we will need to postpone the meeting to next week. Meanwhile, I created a release plan page with our favorite KIPs, to make sure everyone is on the same page: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 I hope I didn't

[jira] [Comment Edited] (KAFKA-3346) Rename "Mode" to "SslMode"

[ https://issues.apache.org/jira/browse/KAFKA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184069#comment-15184069 ] Ismael Juma edited comment on KAFKA-3346 at 3/8/16 12:13 AM: - That's true,

[jira] [Commented] (KAFKA-3346) Rename "Mode" to "SslMode"

[ https://issues.apache.org/jira/browse/KAFKA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184069#comment-15184069 ] Ismael Juma commented on KAFKA-3346: That's true, it's also used to decide whether to create a

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

+users On Mon, Mar 7, 2016 at 4:09 PM, Jason Gustafson wrote: > Hey Ismael, > > Thanks for bringing this up again. Just a quick question: if we do #1, > then there's no way that a user binary could work against both 0.9 and 0.10 > of kafka-clients, right? I'm not sure if

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

Hey Ismael, Thanks for bringing this up again. Just a quick question: if we do #1, then there's no way that a user binary could work against both 0.9 and 0.10 of kafka-clients, right? I'm not sure if that is much of a problem, but may cause a little pain if a user somehow depends transitively on

[jira] [Commented] (KAFKA-3346) Rename "Mode" to "SslMode"

[ https://issues.apache.org/jira/browse/KAFKA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184063#comment-15184063 ] Rajini Sivaram commented on KAFKA-3346: --- Since Mode is used by both SSL and SASL, perhaps SslMode is

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Gwen, In cases where you want completely different callbacks for different mechanisms, I was thinking that the choice would be between a map of classes (mechanism -> callbackHandler class) or a delegator class that chooses the appropriate callback handler class based on mechanism. I chose the

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Ashish, I'm neutral on this (+0), but would be good to have feedback from Harsha and Parth. If you can get their "sounds good", we can probably get it through fairly soon and in time for 0.10.0. Gwen On Wed, Mar 2, 2016 at 9:47 AM, Ashish Singh wrote: > Here is link to the

Re: [DISCUSS] KIP-45 Standardize all client sequence interaction on j.u.Collection.

Coming back to this, see below. On Wed, Jan 27, 2016 at 9:01 PM, Jason Gustafson wrote: > > 1. For subscribe() and assign(), change the parameter type to collection as > planned in the KIP. This is at least source-compatible, so as long as users > compile against the updated

Re: [VOTE] Release plan - Kafka 0.10.0

+1 On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira wrote: > Greetings Kafka Developer Community, > > As you all know, we have few big features that are almost complete > (Timestamps! Interceptors! Streams!). It is time to start planning our > next release. > > I suggest the

[jira] [Commented] (KAFKA-3347) Configure java to prefer ipv4

[ https://issues.apache.org/jira/browse/KAFKA-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183972#comment-15183972 ] ASF GitHub Bot commented on KAFKA-3347: --- GitHub user jcustenborder opened a pull request:

[GitHub] kafka pull request: KAFKA-3347 - Configure java to prefer ipv4

GitHub user jcustenborder opened a pull request: https://github.com/apache/kafka/pull/1026 KAFKA-3347 - Configure java to prefer ipv4 Modified KAFKA_JVM_PERFORMANCE_OPTS to include -Djava.net.preferIPv4Stack=true. Added an additional space at the end of the string to be consistent

[jira] [Created] (KAFKA-3347) Configure java to prefer ipv4

Jeremy Custenborder created KAFKA-3347: -- Summary: Configure java to prefer ipv4 Key: KAFKA-3347 URL: https://issues.apache.org/jira/browse/KAFKA-3347 Project: Kafka Issue Type:

Re: [VOTE] KIP-33 - Add a time based log index to Kafka

Hi Jun, What do you think about the above solution? I am trying to include KIP-33 into 0.10.0 because the log retention has been a long pending issue. Thanks, Jiangjie (Becket) Qin On Tue, Mar 1, 2016 at 8:18 PM, Becket Qin wrote: > Hi Jun, > > I see. If we only use

[GitHub] kafka pull request: KAFKA-2273: Sticky partition assignment strate...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1020 --- 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

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183906#comment-15183906 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian reopened a pull request:

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

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

[GitHub] kafka pull request: KAFKA-2273: Sticky partition assignment strate...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way

[Headsup] Rename "Mode" enum to "SslMode"

Hi, I opened a JIRA to rename the Mode enum, used in channel builders. It is an internal API, so it doesn't require a KIP. But - if you are using this internal API - please shout so we can avoid breaking your code :) https://issues.apache.org/jira/browse/KAFKA-3346 Gwen

[jira] [Created] (KAFKA-3346) Rename "Mode" to "SslMode"

Gwen Shapira created KAFKA-3346: --- Summary: Rename "Mode" to "SslMode" Key: KAFKA-3346 URL: https://issues.apache.org/jira/browse/KAFKA-3346 Project: Kafka Issue Type: Bug Reporter:

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

See Changes: [cshapi] KAFKA-3339: Fix java docs for seekToEnd and seekToBeginning. [cshapi] MINOR: streams javadoc corrections [cshapi] KAFKA-3341: Improve error handling on invalid requests

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183871#comment-15183871 ] Ismael Juma commented on KAFKA-3173: Checked with [~fpj] and he said he would take a look. > Error

[jira] [Updated] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3173: --- Assignee: Flavio Junqueira > Error while moving some partitions to OnlinePartition state >

[jira] [Comment Edited] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183815#comment-15183815 ] Christian Posta edited comment on KAFKA-2967 at 3/7/16 10:05 PM: - All,

[jira] [Commented] (KAFKA-2967) Move Kafka documentation to ReStructuredText

[ https://issues.apache.org/jira/browse/KAFKA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183815#comment-15183815 ] Christian Posta commented on KAFKA-2967: All, I've got a quick spike of converting docs to

[jira] [Commented] (KAFKA-3312) Add a offsets methods to ZkUtils and replace relevant usages

[ https://issues.apache.org/jira/browse/KAFKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183797#comment-15183797 ] ASF GitHub Bot commented on KAFKA-3312: --- GitHub user vahidhashemian opened a pull request:

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Hi, Before I can vote on this KIP, I have two additional questions / comments on the new configuration: 1. sasl.callback.handler.class - it looks like we want a single class that implements all mechanisms. I think this will make it difficult to extend since the only way I can add a mechanism

[GitHub] kafka pull request: KAFKA-3312: Add utility offset methods to ZkUt...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka KAFKA-3312

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183782#comment-15183782 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian reopened a pull request:

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

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

[GitHub] kafka pull request: KAFKA-2273: Sticky partition assignment strate...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1020 --- 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

[GitHub] kafka pull request: KAFKA-2273: Sticky partition assignment strate...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1020 KAFKA-2273: Sticky partition assignment strategy This PR implements a new partition assignment strategy called "sticky", and it's purpose is to balance partitions across consumers in a way

RE: [VOTE] KIP-43: Kafka SASL enhancements

+1 (non-binding) > From: ism...@juma.me.uk > Date: Mon, 7 Mar 2016 19:52:11 + > Subject: Re: [VOTE] KIP-43: Kafka SASL enhancements > To: dev@kafka.apache.org > > +1 (non-binding) > > On Thu, Mar 3, 2016 at 10:37 AM, Rajini Sivaram < >

[jira] [Updated] (KAFKA-3345) ProducerResponse could gracefully handle no throttle time provided

[ https://issues.apache.org/jira/browse/KAFKA-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Baugher updated KAFKA-3345: - Description: When doing some compatibility testing between kafka 0.8 and 0.9 I found that the

[jira] [Created] (KAFKA-3345) ProducerResponse could gracefully handle no throttle time provided

Bryan Baugher created KAFKA-3345: Summary: ProducerResponse could gracefully handle no throttle time provided Key: KAFKA-3345 URL: https://issues.apache.org/jira/browse/KAFKA-3345 Project: Kafka

[jira] [Updated] (KAFKA-3344) Remove previous system test's leftover test-log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3344: -- Status: Patch Available (was: Open) > Remove previous system test's leftover

[GitHub] kafka pull request: KAFKA-3344: Remove previous system test's left...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1024 KAFKA-3344: Remove previous system test's leftover test-log4j.properties You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka

[jira] [Commented] (KAFKA-3344) Remove previous system test's leftover test-log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183718#comment-15183718 ] ASF GitHub Bot commented on KAFKA-3344: --- GitHub user SinghAsDev opened a pull request:

[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0

[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3343: Status: Patch Available (was: Open) > GroupMetadataManager should use NoTimestamp for message v0 >

[jira] [Commented] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0

[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15183715#comment-15183715 ] ASF GitHub Bot commented on KAFKA-3343: --- GitHub user becketqin opened a pull request:

[GitHub] kafka pull request: KAFKA-3343: Use NoTimestamp in GroupMetadataMa...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1023 KAFKA-3343: Use NoTimestamp in GroupMetadataManager when message v0 i… …s used. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-3344) Remove previous system test's leftover test-log4j.properties

Ashish K Singh created KAFKA-3344: - Summary: Remove previous system test's leftover test-log4j.properties Key: KAFKA-3344 URL: https://issues.apache.org/jira/browse/KAFKA-3344 Project: Kafka

[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0

[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3343: --- Priority: Blocker (was: Major) > GroupMetadataManager should use NoTimestamp for message v0 >

  1   2   >