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

See Changes: [wangguoz] KAFKA-2017: Persist Group Metadata and Assignment before Responding -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubun

[GitHub] kafka pull request: KAFKA-2017: Persist Group Metadata and Assignm...

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

[jira] [Commented] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

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

[jira] [Resolved] (KAFKA-2239) Allow coordinator to aggresively remove group when it is no longer owning the group

[ https://issues.apache.org/jira/browse/KAFKA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2239. -- Resolution: Fixed This is resolved as part of KAFKA-2017. > Allow coordinator to aggresively re

[jira] [Resolved] (KAFKA-2018) Add metadata to consumer registry info

[ https://issues.apache.org/jira/browse/KAFKA-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2018. -- Resolution: Fixed This is solved as part of KAFKA-2017. > Add metadata to consumer registry inf

[jira] [Updated] (KAFKA-2017) Persist Coordinator State for Coordinator Failover

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

[jira] [Updated] (KAFKA-2018) Add metadata to consumer registry info

[ https://issues.apache.org/jira/browse/KAFKA-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2018: - Fix Version/s: (was: 0.10.0.0) 0.9.0.0 > Add metadata to consumer registry

[jira] [Commented] (KAFKA-2698) add paused API

[ https://issues.apache.org/jira/browse/KAFKA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986779#comment-14986779 ] Guozhang Wang commented on KAFKA-2698: -- I think it is OK to not include this ticket;

[jira] [Commented] (KAFKA-2698) add paused API

[ https://issues.apache.org/jira/browse/KAFKA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986776#comment-14986776 ] Jun Rao commented on KAFKA-2698: [~guozhang], is this an 0.9.0 blocker? > add paused API

[jira] [Commented] (KAFKA-2702) ConfigDef toHtmlTable() sorts in a way that is a bit confusing

[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986744#comment-14986744 ] Jun Rao commented on KAFKA-2702: [~granthenke], we can probably do the following. 1. Remo

[jira] [Commented] (KAFKA-2697) add leave group logic to the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986555#comment-14986555 ] Onur Karaman commented on KAFKA-2697: - Unfortunately on a tight schedule for something

Re: 0.9.0 release branch

Thanks, Jun. We will switch clients shortly after the release. Cliff > On Nov 2, 2015, at 7:26 PM, Jun Rao wrote: > > Cliff, > > We try not to patch the old consumer too much since we are adding the new > java consumer in 0.9. The new consumer supports callbacks during rebalances > and can ad

Re: [DISCUSS] KIP-36 - Rack aware replica assignment

I think this sounds reasonable. Anyone else have comments? Aditya On Tue, Oct 27, 2015 at 5:23 PM, Allen Wang wrote: > During the discussion in the hangout, it was mentioned that it would be > desirable that consumers know the rack information of the brokers so that > they can consume from the

[jira] [Commented] (KAFKA-2674) ConsumerRebalanceListener.onPartitionsRevoked() is not called on consumer close

[ https://issues.apache.org/jira/browse/KAFKA-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986541#comment-14986541 ] Jiangjie Qin commented on KAFKA-2674: - Yes, I agree documenting it clearly is probably

[jira] [Commented] (KAFKA-2674) ConsumerRebalanceListener.onPartitionsRevoked() is not called on consumer close

[ https://issues.apache.org/jira/browse/KAFKA-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986470#comment-14986470 ] Jason Gustafson commented on KAFKA-2674: [~guozhang] [~becket_qin] Since none of t

Re: 0.9.0 release branch

Cliff, We try not to patch the old consumer too much since we are adding the new java consumer in 0.9. The new consumer supports callbacks during rebalances and can address the problem in KAFKA-2725 better. Thanks, Jun On Mon, Nov 2, 2015 at 11:16 AM, Cliff Rhyne wrote: > Hi Jun, > > I openne

[jira] [Commented] (KAFKA-2702) ConfigDef toHtmlTable() sorts in a way that is a bit confusing

[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986371#comment-14986371 ] Grant Henke commented on KAFKA-2702: [~ijuma] I agree. This would be fairly simple in

Re: 0.9.0 release branch

I added KAFKA-2698 as an 0.9.0.0 blocker. It adds an API to query the currently paused partitions. Here's the PR: https://github.com/apache/kafka/pull/403 On Mon, Nov 2, 2015 at 11:16 AM, Cliff Rhyne wrote: > Hi Jun, > > I openned KAFKA-2725 bas

[jira] [Updated] (KAFKA-2722) Improve ISR change propagation

[ https://issues.apache.org/jira/browse/KAFKA-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2722: Status: Patch Available (was: Open) > Improve ISR change propagation >

[jira] [Updated] (KAFKA-2724) Document ZooKeeper authentication

[ https://issues.apache.org/jira/browse/KAFKA-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2724: Status: Patch Available (was: Open) > Document ZooKeeper authentication >

[jira] [Created] (KAFKA-2727) initialize only the part of the topology relevant to the task

Yasuhiro Matsuda created KAFKA-2727: --- Summary: initialize only the part of the topology relevant to the task Key: KAFKA-2727 URL: https://issues.apache.org/jira/browse/KAFKA-2727 Project: Kafka

[jira] [Updated] (KAFKA-2698) add paused API

[ https://issues.apache.org/jira/browse/KAFKA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-2698: Priority: Blocker (was: Major) > add paused API > -- > > Key: KAFKA-269

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

See Changes: [wangguoz] KAFKA-2707: make KStream processor names deterministic -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (Ubuntu ubuntu

[jira] [Commented] (KAFKA-2697) add leave group logic to the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986229#comment-14986229 ] Guozhang Wang commented on KAFKA-2697: -- [~onurkaraman] assigning the ticket to you no

[jira] [Updated] (KAFKA-2697) add leave group logic to the consumer

[ https://issues.apache.org/jira/browse/KAFKA-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2697: - Assignee: Onur Karaman > add leave group logic to the consumer > -

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

See Changes: [wangguoz] KAFKA-2706: make state stores first class citizens in the processor [wangguoz] KAFKA-2726: Fix port collision between ntpdate and ntp daemon -- [...truncated 3773 lines...

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

See Changes: [wangguoz] KAFKA-2726: Fix port collision between ntpdate and ntp daemon [wangguoz] KAFKA-2707: make KStream processor names deterministic -- [...truncated 37 lines...] :examples:cl

[jira] [Commented] (KAFKA-2724) Document ZooKeeper authentication

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

[GitHub] kafka pull request: KAFKA-2724: ZK Auth documentation.

GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/409 KAFKA-2724: ZK Auth documentation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/fpj/kafka KAFKA-2724 Alternatively you can review and apply these

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

See

[jira] [Updated] (KAFKA-2707) Make KStream processor names deterministic

[ https://issues.apache.org/jira/browse/KAFKA-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2707: - Assignee: Yasuhiro Matsuda > Make KStream processor names deterministic >

[jira] [Commented] (KAFKA-2707) Make KStream processor names deterministic

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

[jira] [Resolved] (KAFKA-2707) Make KStream processor names deterministic

[ https://issues.apache.org/jira/browse/KAFKA-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2707. -- Resolution: Fixed Fix Version/s: 0.9.0.0 Issue resolved by pull request 408 [https://gith

[GitHub] kafka pull request: KAFKA-2707: make KStream processor names deter...

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

[GitHub] kafka pull request: Modified the async producer so it re-queues fa...

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

[jira] [Commented] (KAFKA-2726) ntpdate causes vagrant provision to fail if ntp running

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

[jira] [Resolved] (KAFKA-2726) ntpdate causes vagrant provision to fail if ntp running

[ https://issues.apache.org/jira/browse/KAFKA-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2726. -- Resolution: Fixed Fix Version/s: 0.9.0.0 Issue resolved by pull request 407 [https://gith

[GitHub] kafka pull request: KAFKA-2726: Fix port collision between ntpdate...

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

[jira] [Commented] (KAFKA-2707) Make KStream processor names deterministic

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

[GitHub] kafka pull request: KAFKA-2707: make KStream processor names deter...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/408 KAFKA-2707: make KStream processor names deterministic @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka kstream_pro

[jira] [Resolved] (KAFKA-2706) Make state stores first class citizens in the processor DAG

[ https://issues.apache.org/jira/browse/KAFKA-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-2706. -- Resolution: Fixed Fix Version/s: 0.9.0.0 Issue resolved by pull request 387 [https://gith

[jira] [Commented] (KAFKA-2706) Make state stores first class citizens in the processor DAG

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

[GitHub] kafka pull request: KAFKA-2706: make state stores first class citi...

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

[jira] [Commented] (KAFKA-2719) Kafka classpath has grown too large and breaks some system tests

[ https://issues.apache.org/jira/browse/KAFKA-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986056#comment-14986056 ] Geoff Anderson commented on KAFKA-2719: --- [~rsivaram] Unfortunately we don't have thi

[jira] [Commented] (KAFKA-2726) ntpdate causes vagrant provision to fail if ntp running

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

[GitHub] kafka pull request: KAFKA-2726: Fix port collision between ntpdate...

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/407 KAFKA-2726: Fix port collision between ntpdate and ntp daemon @gwenshap Can you take a quick look? I have verified the change allows successful `vagrant provision` even with ntp daemon already runni

[jira] [Created] (KAFKA-2726) ntpdate causes vagrant provision to fail if ntp running

Geoff Anderson created KAFKA-2726: - Summary: ntpdate causes vagrant provision to fail if ntp running Key: KAFKA-2726 URL: https://issues.apache.org/jira/browse/KAFKA-2726 Project: Kafka Issue

[jira] [Commented] (KAFKA-2658) Implement SASL/PLAIN

[ https://issues.apache.org/jira/browse/KAFKA-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985939#comment-14985939 ] Jun Rao commented on KAFKA-2658: [~rsivaram], yes, perhaps enforcing that SASL/PLAIN can o

[jira] [Commented] (KAFKA-2723) Standardize new consumer exceptions

[ https://issues.apache.org/jira/browse/KAFKA-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985921#comment-14985921 ] Guozhang Wang commented on KAFKA-2723: -- Thanks [~hachikuji], a few clarification ques

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

See Changes: [wangguoz] KAFKA-2518: Update NOTICE file -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (docker Ubuntu ubuntu) in worksp

[jira] [Commented] (KAFKA-2719) Kafka classpath has grown too large and breaks some system tests

[ https://issues.apache.org/jira/browse/KAFKA-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985881#comment-14985881 ] Rajini Sivaram commented on KAFKA-2719: --- [~geoffra] If system tests are guaranteed t

[jira] [Updated] (KAFKA-2285) Logging trait obfuscates call site information

[ https://issues.apache.org/jira/browse/KAFKA-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2285: --- Assignee: (was: Grant Henke) > Logging trait obfuscates call site information > --

[jira] [Updated] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2580: --- Assignee: (was: Grant Henke) > Kafka Broker keeps file handles open for all log files (even if its

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985875#comment-14985875 ] Grant Henke commented on KAFKA-2580: Marking as Unassigned as I need to shift my focus

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

See Changes: [cshapi] KAFKA-2681: Added SASL documentation [wangguoz] KAFKA-2518: Update NOTICE file -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotel

Re: 0.9.0 release branch

Hi Jun, I openned KAFKA-2725 based on my experience with duplicate message processing with auto-commit off. I think it's a fairly small change, especially for someone familiar with the kafka code-base but it makes a big impact for clients not using auto-commit. Can this be included in 0.9.0? Th

[jira] [Commented] (KAFKA-2719) Kafka classpath has grown too large and breaks some system tests

[ https://issues.apache.org/jira/browse/KAFKA-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985813#comment-14985813 ] Geoff Anderson commented on KAFKA-2719: --- [~rsivaram] I wonder if this problem is bet

[jira] [Created] (KAFKA-2725) high level consumer rebalances with auto-commit disabled should throw an exception

Cliff Rhyne created KAFKA-2725: -- Summary: high level consumer rebalances with auto-commit disabled should throw an exception Key: KAFKA-2725 URL: https://issues.apache.org/jira/browse/KAFKA-2725 Project:

[jira] [Updated] (KAFKA-2441) SSL/TLS in official docs

[ https://issues.apache.org/jira/browse/KAFKA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2441: Status: Patch Available (was: Open) > SSL/TLS in official docs > > >

[jira] [Commented] (KAFKA-2518) Update NOTICE file

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

[jira] [Updated] (KAFKA-2518) Update NOTICE file

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

[GitHub] kafka pull request: KAFKA-2518: Update NOTICE file

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

[jira] [Commented] (KAFKA-2441) SSL/TLS in official docs

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

[GitHub] kafka pull request: KAFKA-2441: SSL/TLS in official docs

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/406 KAFKA-2441: SSL/TLS in official docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka KAFKA-2441 Alternatively you can review and

Re: 0.9.0 release branch

I added KAFKA-2691 as well, which improves client handling of authorization errors. -Jason On Mon, Nov 2, 2015 at 10:25 AM, Becket Qin wrote: > Hi Jun, > > I added KAFKA-2722 as a blocker for 0.9. It fixes the ISR propagation > scalability issue we saw. > > Thanks, > > Jiangjie (Becket) Qin > >

[jira] [Updated] (KAFKA-2691) Improve handling of authorization failure during metadata refresh

[ https://issues.apache.org/jira/browse/KAFKA-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2691: --- Priority: Blocker (was: Major) > Improve handling of authorization failure during metadata re

[jira] [Commented] (KAFKA-2716) Make Kafka core not depend on log4j-appender

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

[GitHub] kafka pull request: KAFKA-2716: Make Kafka core not depend on log4...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/405 KAFKA-2716: Make Kafka core not depend on log4j-appender You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-2716 Alternat

[jira] [Commented] (KAFKA-2658) Implement SASL/PLAIN

[ https://issues.apache.org/jira/browse/KAFKA-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985751#comment-14985751 ] Rajini Sivaram commented on KAFKA-2658: --- [~junrao] As described in the RFC for SASL/

[jira] [Commented] (KAFKA-2716) Make Kafka core not depend on log4j-appender

[ https://issues.apache.org/jira/browse/KAFKA-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985750#comment-14985750 ] Ashish K Singh commented on KAFKA-2716: --- [~ijuma], [~gwenshap] I agree that not brea

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

See Changes: [cshapi] KAFKA-2681: Added SASL documentation -- [...truncated 67 lines...] ^

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985707#comment-14985707 ] Vinoth Chandar commented on KAFKA-2580: --- [~jkreps] ah ok. point taken :) > Kafka B

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

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-2528. - Resolution: Fixed > Quota Performance Evaluation > > > Key: K

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

[ https://issues.apache.org/jira/browse/KAFKA-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985697#comment-14985697 ] Jay Kreps commented on KAFKA-2528: -- [~lindong] Great! > Quota Performance Evaluation > -

[jira] [Commented] (KAFKA-2580) Kafka Broker keeps file handles open for all log files (even if its not written to/read from)

[ https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985696#comment-14985696 ] Jay Kreps commented on KAFKA-2580: -- [~vinothchandar] All I'm saying is that you have to k

[jira] [Updated] (KAFKA-2681) SASL authentication in official docs

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

[jira] [Commented] (KAFKA-2681) SASL authentication in official docs

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

Re: 0.9.0 release branch

Hi Jun, I added KAFKA-2722 as a blocker for 0.9. It fixes the ISR propagation scalability issue we saw. Thanks, Jiangjie (Becket) Qin On Mon, Nov 2, 2015 at 9:16 AM, Jun Rao wrote: > Hi, everyone, > > We are getting close to the 0.9.0 release. The current plan is to have the > following remai

[jira] [Commented] (KAFKA-2722) Improve ISR change propagation

[ https://issues.apache.org/jira/browse/KAFKA-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985687#comment-14985687 ] ASF GitHub Bot commented on KAFKA-2722: --- GitHub user becketqin reopened a pull reque

[jira] [Commented] (KAFKA-2722) Improve ISR change propagation

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

[GitHub] kafka pull request: KAFKA-2722: Improve ISR change propagation.

GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/402 KAFKA-2722: Improve ISR change propagation. The patch has two changes: 1. fixed a bug in controller that it sends UpdateMetadataRequest of all the partitions in the cluster. 2. Uses the f

[GitHub] kafka pull request: KAFKA-2722: Improve ISR change propagation.

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

[GitHub] kafka pull request: Improve ISR change propagation.

GitHub user becketqin reopened a pull request: https://github.com/apache/kafka/pull/402 Improve ISR change propagation. The patch has two changes: 1. fixed a bug in controller that it sends UpdateMetadataRequest of all the partitions in the cluster. 2. Uses the following rul

[jira] [Commented] (KAFKA-2441) SSL/TLS in official docs

[ https://issues.apache.org/jira/browse/KAFKA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985681#comment-14985681 ] Sriharsha Chintalapani commented on KAFKA-2441: --- [~gwenshap] Please go ahead

[jira] [Commented] (KAFKA-2441) SSL/TLS in official docs

[ https://issues.apache.org/jira/browse/KAFKA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985672#comment-14985672 ] Gwen Shapira commented on KAFKA-2441: - [~harsha_ch], if you are busy, mind if I pick t

[GitHub] kafka pull request: KAFKA-2681: Added SASL documentation. It doesn...

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

[GitHub] kafka pull request: Improve ISR change propagation.

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

[jira] [Updated] (KAFKA-2722) Improve ISR change propagation

[ https://issues.apache.org/jira/browse/KAFKA-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2722: Priority: Blocker (was: Major) > Improve ISR change propagation > -- >

[jira] [Updated] (KAFKA-2722) Improve ISR change propagation

[ https://issues.apache.org/jira/browse/KAFKA-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2722: Fix Version/s: 0.9.0.0 > Improve ISR change propagation > -- > >

[jira] [Commented] (KAFKA-2658) Implement SASL/PLAIN

[ https://issues.apache.org/jira/browse/KAFKA-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985663#comment-14985663 ] Jun Rao commented on KAFKA-2658: [~rsivaram], we had a chat with a security consulting fir

[jira] [Commented] (KAFKA-2255) Missing documentation for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985657#comment-14985657 ] Gwen Shapira commented on KAFKA-2255: - Actually, for 0.9.0.0 we will automatically gen

[jira] [Resolved] (KAFKA-2255) Missing documentation for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-2255. - Resolution: Fixed > Missing documentation for max.in.flight.requests.per.connection >

Re: unsubcribe

I think this should be sent to dev-unsubscr...@kafka.apache.org. Source: http://kafka.apache.org/contact.html Thanks, Grant On Mon, Nov 2, 2015 at 7:49 AM, Sungju Bong wrote: > > -- Grant Henke Software Engineer | Cloudera gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke

[jira] [Commented] (KAFKA-2724) Document ZooKeeper authentication

[ https://issues.apache.org/jira/browse/KAFKA-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985606#comment-14985606 ] Flavio Junqueira commented on KAFKA-2724: - A security.html file is being introduce

[jira] [Updated] (KAFKA-2518) Update NOTICE file

[ https://issues.apache.org/jira/browse/KAFKA-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2518: Status: Patch Available (was: Open) > Update NOTICE file > -- > > K

[jira] [Updated] (KAFKA-2681) SASL authentication in official docs

[ https://issues.apache.org/jira/browse/KAFKA-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2681: Status: Patch Available (was: Open) > SASL authentication in official docs > --

[GitHub] kafka pull request: KAFKA-2518: Update NOTICE file

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/404 KAFKA-2518: Update NOTICE file You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka KAFKA-2518 Alternatively you can review and apply

[jira] [Commented] (KAFKA-2518) Update NOTICE file

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

[jira] [Assigned] (KAFKA-2518) Update NOTICE file

[ https://issues.apache.org/jira/browse/KAFKA-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira reassigned KAFKA-2518: --- Assignee: Gwen Shapira > Update NOTICE file > -- > > Key: KAF

0.9.0 release branch

Hi, everyone, We are getting close to the 0.9.0 release. The current plan is to have the following remaining 0.9.0 blocker issues resolved this week, cut the 0.9.0 release branch by Nov. 6 (Friday) and start the RC on Nov. 9 (Monday). https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAF

  1   2   >