[jira] [Commented] (KAFKA-2431) Test SSL/TLS impact on performance

[ https://issues.apache.org/jira/browse/KAFKA-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182739#comment-15182739 ] Ismael Juma commented on KAFKA-2431: Hi [~ssuo], an OpenSSL-based implementation is no

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182767#comment-15182767 ] Aleksandar Stojadinovic commented on KAFKA-3334: Sure :) . > First messag

[jira] [Commented] (KAFKA-3326) Error: A JNI error has occurred, please check your installation and try again

[ https://issues.apache.org/jira/browse/KAFKA-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182774#comment-15182774 ] iyaozhen commented on KAFKA-3326: - Oh no. It is my problem. MD5 (kafka_2.11-0.9.0.1.tgz)

[GitHub] kafka pull request: MINOR: streams javadoc corrections

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1019 MINOR: streams javadoc corrections You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka JAVADOC Alternatively you can review and app

[jira] [Closed] (KAFKA-2354) setting log.dirs property makes tools fail if there is a comma

[ https://issues.apache.org/jira/browse/KAFKA-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Graff closed KAFKA-2354. > setting log.dirs property makes tools fail if there is a comma > -

[jira] [Created] (KAFKA-3342) https://cwiki.apache.org/confluence/display/KAFKA/Log+Compaction has log.cleaner.min.cleanable.ratio listed twice in error

Michael Graff created KAFKA-3342: Summary: https://cwiki.apache.org/confluence/display/KAFKA/Log+Compaction has log.cleaner.min.cleanable.ratio listed twice in error Key: KAFKA-3342 URL: https://issues.apache.org

[jira] [Commented] (KAFKA-3064) Improve resync method to waste less time and data transfer

[ https://issues.apache.org/jira/browse/KAFKA-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183141#comment-15183141 ] Michael Graff commented on KAFKA-3064: -- As we have added two more brokers (bringing o

[VOTE] Release plan - Kafka 0.10.0

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 following: * Cut branches on March 21st * Publish the first release candidate the next day * S

Re: [VOTE] Release plan - Kafka 0.10.0

+1 quick question/definition for the release cut (assuming vote passes) your proposing please. Critical bug fixes for new features and regression or just regression and new feature can get pulled if not working right if less impactful to-do so? Understandably that is dependent on the feature and/

[jira] [Updated] (KAFKA-3297) More optimally balanced partition assignment strategy (new consumer)

[ https://issues.apache.org/jira/browse/KAFKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Olson updated KAFKA-3297: Fix Version/s: 0.10.0.0 > More optimally balanced partition assignment strategy (new consumer) > ---

[jira] [Updated] (KAFKA-2435) More optimally balanced partition assignment strategy

[ https://issues.apache.org/jira/browse/KAFKA-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Olson updated KAFKA-2435: Fix Version/s: 0.10.0.0 > More optimally balanced partition assignment strategy > --

[jira] [Updated] (KAFKA-2434) remove roundrobin identical topic constraint in consumer coordinator (old API)

[ https://issues.apache.org/jira/browse/KAFKA-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Olson updated KAFKA-2434: Fix Version/s: 0.10.0.0 > remove roundrobin identical topic constraint in consumer coordinator (old

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

+1 On Thu, Mar 3, 2016 at 2:36 PM, Ismael Juma wrote: > Hi all, > > The new Java producer was introduced in 0.8.2.0 (released in February > 2015). It has become the default implementation for various tools since > 0.9.0.0 (released in October 2015) and it is the only implementation with > suppor

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

Hey Andrew, Thanks for adding the example. No I don't think we have a jira open for that issue. I'm not sure if we need to fix it in roundrobin (now that it's already out there and some may be using it) vs. just going with your new "fair" strategy and maybe add a new explicit roundrobinv2. Thanks

[jira] [Commented] (KAFKA-3233) Per topic consumer metrics missing in new consumer's metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183449#comment-15183449 ] Yifan Ying commented on KAFKA-3233: --- Hi Guozhang, thanks for merging my change. Is there

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

GitHub user vahidhashemian opened 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 th

Re: [DISCUSS] KIP-35 - Retrieve protocol version

On Fri, Mar 4, 2016 at 5:46 PM, Jay Kreps wrote: > Hey Ashish, > > Both good points. > > I think the issue with the general metadata request is the same as the > issue with a version-specific metadata request from the other > proposal--basically it's a chicken and egg problem, to find out anythin

[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&focusedCommentId=15183462#comment-15183462 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian opened a pull re

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

+1 On Mon, Mar 7, 2016 at 10:16 AM, Joel Koshy wrote: > +1 > > On Thu, Mar 3, 2016 at 2:36 PM, Ismael Juma wrote: > > > Hi all, > > > > The new Java producer was introduced in 0.8.2.0 (released in February > > 2015). It has become the default implementation for various tools since > > 0.9.0.0 (

[jira] [Commented] (KAFKA-3233) Per topic consumer metrics missing in new consumer's metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183502#comment-15183502 ] Gwen Shapira commented on KAFKA-3233: - Since the change was merged into trunk, it will

[GitHub] kafka pull request: KAFKA-3339: Fix java docs for seekToEnd and se...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1021 KAFKA-3339: Fix java docs for seekToEnd and seekToBeginning. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-3339 Alt

[jira] [Commented] (KAFKA-3339) org.apache.kafka.clients.consumer.KafkaConsumer javadoc for seekToBeginning, seekToEnd incomplete

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

Re: [VOTE] Release plan - Kafka 0.10.0

+1 On Mon, Mar 7, 2016 at 9:42 AM, Joe Stein wrote: > +1 > > quick question/definition for the release cut (assuming vote passes) your > proposing please. > > Critical bug fixes for new features and regression or just regression and > new feature can get pulled if not working right if less impac

Re: [VOTE] Release plan - Kafka 0.10.0

Hi Joe, The branch cutting means that new features will go into trunk, bug fixes will go into either trunk and branch or just trunk - depending on committer decision. Committers should take into consideration the importance of the fix vs the stability of the planned release. I don't have specific

[jira] [Commented] (KAFKA-3339) org.apache.kafka.clients.consumer.KafkaConsumer javadoc for seekToBeginning, seekToEnd incomplete

[ https://issues.apache.org/jira/browse/KAFKA-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183517#comment-15183517 ] Ashish K Singh commented on KAFKA-3339: --- [~haraldk] could you review the PR. Thanks

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (binding) On Mon, Mar 7, 2016 at 11:26 AM, Gwen Shapira wrote: > Hi Joe, > > The branch cutting means that new features will go into trunk, bug > fixes will go into either trunk and branch or just trunk - depending > on committer decision. Committers should take into consideration the > impor

[GitHub] kafka pull request: KAFKA-3339: Fix java docs for seekToEnd and se...

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

[jira] [Resolved] (KAFKA-3339) org.apache.kafka.clients.consumer.KafkaConsumer javadoc for seekToBeginning, seekToEnd incomplete

[ https://issues.apache.org/jira/browse/KAFKA-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3339. - Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1021 [https://gith

[jira] [Assigned] (KAFKA-3339) org.apache.kafka.clients.consumer.KafkaConsumer javadoc for seekToBeginning, seekToEnd incomplete

[ https://issues.apache.org/jira/browse/KAFKA-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh reassigned KAFKA-3339: - Assignee: Ashish K Singh > org.apache.kafka.clients.consumer.KafkaConsumer javadoc for se

[jira] [Commented] (KAFKA-3339) org.apache.kafka.clients.consumer.KafkaConsumer javadoc for seekToBeginning, seekToEnd incomplete

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

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) Ismael On Mon, Mar 7, 2016 at 7:27 PM, Neha Narkhede wrote: > +1 (binding) > > On Mon, Mar 7, 2016 at 11:26 AM, Gwen Shapira wrote: > > > Hi Joe, > > > > The branch cutting means that new features will go into trunk, bug > > fixes will go into either trunk and branch or just t

[GitHub] kafka pull request: MINOR: streams javadoc corrections

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

[jira] [Commented] (KAFKA-3341) Improve error handling on invalid requests

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

[GitHub] kafka pull request: KAFKA-3341: Improve error handling on invalid ...

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

[jira] [Updated] (KAFKA-3341) Improve error handling on invalid requests

[ https://issues.apache.org/jira/browse/KAFKA-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3341: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 10

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

It will be good to get the SASL enhancements into 0.10.0.0 if possible. There are no outstanding questions related to the KIP and the PR is ready for review. Feedback is appreciated. Thank you... On Thu, Mar 3, 2016 at 10:37 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > > I would

[GitHub] kafka pull request: KAFKA-3334: Add a note on potential message lo...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1022 KAFKA-3334: Add a note on potential message loss while using auto top… …ics creation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Sing

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

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

Build failed in Jenkins: kafka-trunk-jdk7 #1095

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 -

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

+1 (non-binding) On Thu, Mar 3, 2016 at 10:37 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > I would like to start the voting process for *KIP-43: Kafka SASL > enhancements*. This KIP extends the SASL implementation in Kafka to support > new SASL mechanisms to enable Kafka to be inte

KIP call to discuss some of the outstanding KIPs

Hello Jun, Could we have a KIP call tomorrow to discuss some of the outstanding KIPs. As 0.10 code freeze date, as per current suggestion, is fast approaching, it will really help out with moving forward with following KIPs. * KIP-4: Command line and centralized operations * KIP-35: Retrieve prot

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183597#comment-15183597 ] Aleksandar Stojadinovic commented on KAFKA-3334: The addition sounds very

[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

[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 feature

[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&focusedCommentId=15183600#comment-15183600 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian reopened a pull

[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&focusedCommentId=15183599#comment-15183599 ] ASF GitHub Bot commented on KAFKA-2273: --- Github user vahidhashemian closed the pull

[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: Fix Version/s: 0.10.0.0 > GroupMetadataManager should use NoTimestamp for message v0 > -

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

Jiangjie Qin created KAFKA-3343: --- Summary: GroupMetadataManager should use NoTimestamp for message v0 Key: KAFKA-3343 URL: https://issues.apache.org/jira/browse/KAFKA-3343 Project: Kafka Issue

[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: --- Reviewer: Jun Rao > GroupMetadataManager should use NoTimestamp for message v0 > -

[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 > ---

[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

[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 https://github.com/becketqin/k

[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&focusedCommentId=15183715#comment-15183715 ] ASF GitHub Bot commented on KAFKA-3343: --- GitHub user becketqin 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-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&focusedCommentId=15183718#comment-15183718 ] ASF GitHub Bot commented on KAFKA-3344: --- GitHub user SinghAsDev opened a pull reques

[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 KAF

[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 test-log4j.propert

[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-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 old

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 < > rajinisiva...@goo

[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

[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 feature

[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&focusedCommentId=15183782#comment-15183782 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian reopened a pull

[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&focusedCommentId=15183781#comment-15183781 ] ASF GitHub Bot commented on KAFKA-2273: --- Github user vahidhashemian closed the pull

[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 Altern

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 will

[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&focusedCommentId=15183797#comment-15183797 ] ASF GitHub Bot commented on KAFKA-3312: --- GitHub user vahidhashemian opened a pull re

[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&focusedCommentId=15183815#comment-15183815 ] Christian Posta commented on KAFKA-2967: All, I've got a quick spike of convertin

[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&focusedCommentId=15183815#comment-15183815 ] Christian Posta edited comment on KAFKA-2967 at 3/7/16 10:05 PM: ---

[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] [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&focusedCommentId=15183871#comment-15183871 ] Ismael Juma commented on KAFKA-3173: Checked with [~fpj] and he said he would take a l

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] [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:

[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

[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

[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&focusedCommentId=15183905#comment-15183905 ] ASF GitHub Bot commented on KAFKA-2273: --- Github user vahidhashemian closed the pull

[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 feature

[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&focusedCommentId=15183906#comment-15183906 ] ASF GitHub Bot commented on KAFKA-2273: --- GitHub user vahidhashemian reopened a pull

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 index.interval.bytes, the

[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: Improveme

[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] [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&focusedCommentId=15183972#comment-15183972 ] ASF GitHub Bot commented on KAFKA-3347: --- GitHub user jcustenborder opened a pull req

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 following: > * Cut branc

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 release, there shoul

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 KIP, > https://cwiki.

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 latt

[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&focusedCommentId=15184063#comment-15184063 ] Rajini Sivaram commented on KAFKA-3346: --- Since Mode is used by both SSL and SASL, pe

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 d

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 that is much of a proble

[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&focusedCommentId=15184069#comment-15184069 ] Ismael Juma commented on KAFKA-3346: That's true, it's also used to decide whether to

[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&focusedCommentId=15184069#comment-15184069 ] Ismael Juma edited comment on KAFKA-3346 at 3/8/16 12:13 AM: -

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 mi

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 > make sure everyone is

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: [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 supported >princip

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 Developer Community, > > > > As you all know,

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 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 wrote:

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 chan

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 delegation tokens to Kafka >

  1   2   >