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

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954511#comment-14954511 ] Ewen Cheslack-Postava commented on KAFKA-2477: -- [~cpsoman] Beyond applying to

Re: [kafka-clients] Kafka 0.9.0 release branch

Not sure if I'd call it a blocker, but if we can get it in I would *really* like to see some solution to https://issues.apache.org/jira/browse/KAFKA-2397 committed. Without an explicit leave group, even normal operation of groups can leave some partitions unprocessed for 30-60s at a time under *nor

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

I wonder if we need to solve the error problem? I think this KIP gives a descent work around. Probably we should have included an error in the response header, but we debated it at the time decided not to and now it is pretty hard to add because the headers aren't versioned (d'oh). It seems like

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

See -- [...truncated 322 lines...] :kafka-trunk-jdk7:clients:jar UP-TO-DATE :kafka-trunk-jdk7:clients:javadoc UP-TO-DATE :kafka-trunk-jdk7:log4j-appender:compileJava UP-TO-DATE :kafka-trunk-jdk7:log4j-app

[GitHub] kafka pull request: let kafka support "commit offset after consumi...

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

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

I am thinking instead of returning an empty response, it would be better to return an explicit UnsupportedVersionException code. Today KafkaApis handles the error in the following way: 1. For requests/responses using old Scala classes, KafkaApis uses RequestOrResponse.handleError() to return an er

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

See

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

This works really nicely from the consumer side, but what about the producer? If there are no more topics,do we allow producing to a directory and have the Partitioner hash-partition messages between all partitions in the multiple levels in a directory? Also, I think we want to preserve the consum

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

See

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Okay this is similar to what I think we have talked about before. Let me elaborate on the idea that I think has been floating around--it's pretty similar with a few differences. I think what you are calling the "default namespace" is basically what I would call the "current working directory" with

[jira] [Updated] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

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

[jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954250#comment-14954250 ] Gwen Shapira commented on KAFKA-2613: - Well, I'm not sure we are any stabler now, but

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

See Changes: [cshapi] KAFKA-2613; Make maxParallelForks configurable via Gradle config so it -- [...truncated 962 lines...] kafka.common.ConfigTest > testInvalidClientIds PASSED kafka.common.ZkNo

[jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954217#comment-14954217 ] Ismael Juma commented on KAFKA-2613: OK, seems sensible to go for stability in the run

[jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954215#comment-14954215 ] Gwen Shapira commented on KAFKA-2613: - 1 :) > Consider capping `maxParallelForks` fo

[jira] [Created] (KAFKA-2636) Producer connectivity obscured connection failure logging

Jason Kania created KAFKA-2636: -- Summary: Producer connectivity obscured connection failure logging Key: KAFKA-2636 URL: https://issues.apache.org/jira/browse/KAFKA-2636 Project: Kafka Issue Typ

[jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954214#comment-14954214 ] Ismael Juma commented on KAFKA-2613: Thanks Gwen and Ewen. What value did you use for

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

See Changes: [cshapi] KAFKA-2613; Make maxParallelForks configurable via Gradle config so it -- [...truncated 207 lines...]

[jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954205#comment-14954205 ] Gwen Shapira commented on KAFKA-2613: - Committed and updated the Jenkins builds. Wait

[GitHub] kafka pull request: KAFKA-2613: Make maxParallelForks configurable...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/293 --- 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-2613) Consider capping `maxParallelForks` for Jenkins builds

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

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

On Mon, Oct 12, 2015 at 5:42 PM, Jay Kreps wrote: > Great. I definitely would strongly favor carrying over user's intuition > from FS unless we think we need a very different model. The minor details > like the seperator and namespace term will help with that. > > Follow-up question, say I have a

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

Two quick pieces of feedback: 1. The use of a version of -1 as magical entry dividing between deprecated versions is a bit hacky. What about instead having an array of supported versions and a separate array of deprecated versions. The deprecated versions would always be a subset of the supported v

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

See Changes: [wangguoz] KAFKA-2581: Run some existing ducktape tests with SSL -- [...truncated 324 lines...] :kafka-trunk-jdk7:log4j-appender:compileJava UP-TO-DATE :kafka-trunk-jdk7:log4j-append

[jira] [Commented] (KAFKA-2581) Run all existing ducktape tests with SSL-enabled clients and brokers

[ https://issues.apache.org/jira/browse/KAFKA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954162#comment-14954162 ] Ismael Juma commented on KAFKA-2581: Thanks for your contribution Rajini and thanks fo

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Great. I definitely would strongly favor carrying over user's intuition from FS unless we think we need a very different model. The minor details like the seperator and namespace term will help with that. Follow-up question, say I have a layout like /chicago-datacenter/user-events/pageviews Can

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Hey Jay, thanks for reviewing the proposal. Answers inline. On Mon, Oct 12, 2015 at 10:53 AM, Jay Kreps wrote: > Hey guys, > > I think this is an important feature and one we've talked about for a > while. I really think trying to invent a new nomenclature is going to make > it hard for people t

[jira] [Commented] (KAFKA-2581) Run all existing ducktape tests with SSL-enabled clients and brokers

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

[GitHub] kafka pull request: KAFKA-2581: Run some existing ducktape tests w...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/271 --- 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] [Updated] (KAFKA-2581) Run all existing ducktape tests with SSL-enabled clients and brokers

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

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Rajini, thanks for the review. Answers inline. On Mon, Oct 12, 2015 at 8:01 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Ashish, > > Thank you for doing this writeup and starting the discussion around > namespaces and multi-tenancy. > > We have implemented a namespace solution on t

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Magnus, thanks for taking a look at the proposal. Answers inline. On Sat, Oct 10, 2015 at 2:03 AM, Magnus Edenhill wrote: > Good write-up Ashish. > > Looking at one of the rejected alternatives got me thinking: > "Modify request/ response formats to take namespace specifically. > > Solves the is

[jira] [Commented] (KAFKA-2598) Add Test with authorizer for producer and consumer

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

[GitHub] kafka pull request: KAFKA-2598: Adding integration test for the au...

GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/kafka/pull/300 KAFKA-2598: Adding integration test for the authorizer at API level. … …Some bug fixes that I encountered while running the tests. You can merge this pull request into a Git repository b

[jira] [Commented] (KAFKA-2490) support new consumer in ConsumerGroupCommand

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

[GitHub] kafka pull request: KAFKA-2490: support new consumer in ConsumerGr...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/299 KAFKA-2490: support new consumer in ConsumerGroupCommand You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA-2490 Alternat

[jira] [Commented] (KAFKA-2209) Change client quotas dynamically using DynamicConfigManager

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

[GitHub] kafka pull request: KAFKA-2209 - Change quotas dynamically using D...

GitHub user auradkar opened a pull request: https://github.com/apache/kafka/pull/298 KAFKA-2209 - Change quotas dynamically using DynamicConfigManager Changes in this patch are: 1. ClientIdConfigHandler now passes through the config changes to the quota manager. 2. Removed s

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

See

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

Our first successful Jenkins JDK 8 build. :) Ismael On 12 Oct 2015 21:40, "Apache Jenkins Server" wrote: > See > >

[jira] [Commented] (KAFKA-2094) Kafka does not create topic automatically after deleting the topic.

[ https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953697#comment-14953697 ] Mayuresh Gharat commented on KAFKA-2094: [~mingfang] We should create a separate J

[jira] [Created] (KAFKA-2635) After deleting the topic, you can still send and receive messages but kafka-topic --list does not show the topic.

Mayuresh Gharat created KAFKA-2635: -- Summary: After deleting the topic, you can still send and receive messages but kafka-topic --list does not show the topic. Key: KAFKA-2635 URL: https://issues.apache.org/jira/

Kafka KIP meeting Oct 13 at 11:00am PST

Hi, Everyone, We will have a Kafka KIP meeting tomorrow at 11:00am PST. If you plan to attend but haven't received an invite, please let me know. The following is the agenda. Agenda: 1. Kafka 0.9.0 release and if time permits, 2. KIP-32: Add CreateTime and LogAppendTime to Kafka message 3. KIP-3

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

See

[jira] [Commented] (KAFKA-2295) Dynamically loaded classes (encoders, etc.) may not be found by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953689#comment-14953689 ] Guozhang Wang commented on KAFKA-2295: -- Pinging [~tdas] once again for validation, or

[jira] [Updated] (KAFKA-2203) Get gradle build to work with Java 8

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

[GitHub] kafka pull request: KAFKA-2203: Getting Java8 to relax about javad...

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

Kafka 0.9.0 release branch

Hi, Everyone, As we are getting closer to the 0.9.0 release, we plan to cut an 0.9.0 release branch in about two weeks from now. In the meantime, we will try to resolve most if not all 0.9.0 blockers listed below. https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20i

[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=14953683#comment-14953683 ] Guozhang Wang commented on KAFKA-2017: -- [~junrao] I agree this should be in 0.9.0 rel

[jira] [Commented] (KAFKA-2203) Get gradle build to work with Java 8

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

[jira] [Updated] (KAFKA-2258) Port mirrormaker_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2258: --- Priority: Major (was: Blocker) > Port mirrormaker_testsuite > -- > >

[jira] [Updated] (KAFKA-2257) port replication_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2257: --- Priority: Major (was: Blocker) > port replication_testsuite > -- > >

[jira] [Updated] (KAFKA-2259) port offset_management_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2259: --- Priority: Major (was: Blocker) > port offset_management_testsuite > > >

[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 ] Jun Rao updated KAFKA-2017: --- Affects Version/s: (was: 0.10.0.0) 0.9.0.0 Fix Version/s: (was: 0.10.0.0

[jira] [Resolved] (KAFKA-2631) Expose data volume via JMX

[ https://issues.apache.org/jira/browse/KAFKA-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-2631. - Resolution: Implemented > Expose data volume via JMX > -- > >

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

See Changes: [jjkoshy] KAFKA-2443 KAFKA-2567; Expose windowSize on Rate; - Throttle time should -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

[jira] [Resolved] (KAFKA-2567) throttle-time shouldn't be NaN

[ https://issues.apache.org/jira/browse/KAFKA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2567. --- Resolution: Fixed Issue resolved by pull request 213 [https://github.com/apache/kafka/pull/213] > thr

[jira] [Commented] (KAFKA-2443) Expose windowSize on Rate

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

[jira] [Resolved] (KAFKA-2443) Expose windowSize on Rate

[ https://issues.apache.org/jira/browse/KAFKA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2443. --- Resolution: Fixed Fix Version/s: 0.9.0.0 Issue resolved by pull request 213 [https://github.com

[GitHub] kafka pull request: KAFKA-2443 Expose windowSize on Rate; KAFKA-25...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/213 --- 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] [Updated] (KAFKA-2515) handle oversized messages properly in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2515: --- Priority: Blocker (was: Major) > handle oversized messages properly in new consumer > ---

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953542#comment-14953542 ] Mike Yoder commented on KAFKA-2629: --- Hi - I work with [~singhashish] so I thought I'd ju

[jira] [Commented] (KAFKA-2487) change kafka.examples.Consumer to use the new java consumer

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

[GitHub] kafka pull request: KAFKA-2487: change kafka.examples.Consumer to ...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/297 KAFKA-2487: change kafka.examples.Consumer to use the new java consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/SinghAsDev/kafka KAFKA

[jira] [Created] (KAFKA-2634) KafkaProducer hangs on future.get()

Jason Kania created KAFKA-2634: -- Summary: KafkaProducer hangs on future.get() Key: KAFKA-2634 URL: https://issues.apache.org/jira/browse/KAFKA-2634 Project: Kafka Issue Type: Bug Affects Ver

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Hey guys, I think this is an important feature and one we've talked about for a while. I really think trying to invent a new nomenclature is going to make it hard for people to understand, though. As such I recommend we call namespaces "directories" and denote them with '/'--this will make the fea

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

See Changes: [cshapi] KAFKA-2633; Default logging from tools to Stderr -- [...truncated 322 lines...] :kafka-trunk-jdk7:clients:jar UP-TO-DATE :kafka-trunk-jdk7:clients:javadoc UP-TO-DATE :kafka-

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

See Changes: [cshapi] KAFKA-2633; Default logging from tools to Stderr -- [...truncated 859 lines...]

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953391#comment-14953391 ] Ismael Juma commented on KAFKA-1804: trunk will be released as 0.9.0.0, see http://se

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953370#comment-14953370 ] Patrick J. McNerthney commented on KAFKA-1804: -- It looks likely fixed in the

[jira] [Updated] (KAFKA-2633) Default logging from tools to Stderr

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

[jira] [Commented] (KAFKA-2633) Default logging from tools to Stderr

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

[GitHub] kafka pull request: KAFKA-2633: Default logging from tools to Stde...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/296 --- 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] [Updated] (KAFKA-2633) Default logging from tools to Stderr

[ https://issues.apache.org/jira/browse/KAFKA-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2633: --- Status: Patch Available (was: Open) > Default logging from tools to Stderr >

[jira] [Assigned] (KAFKA-2633) Default logging from tools to Stderr

[ https://issues.apache.org/jira/browse/KAFKA-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-2633: -- Assignee: Grant Henke > Default logging from tools to Stderr >

[jira] [Commented] (KAFKA-2633) Default logging from tools to Stderr

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

[jira] [Created] (KAFKA-2633) Default logging from tools to Stderr

Grant Henke created KAFKA-2633: -- Summary: Default logging from tools to Stderr Key: KAFKA-2633 URL: https://issues.apache.org/jira/browse/KAFKA-2633 Project: Kafka Issue Type: Bug Re

[GitHub] kafka pull request: KAFKA-2633: Default logging from tools to Stde...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/296 KAFKA-2633: Default logging from tools to Stderr You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka tools-log4j Alternatively y

[jira] [Updated] (KAFKA-2603) Add timeout to ConsoleConsumer running with new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2603: --- Reviewer: Guozhang Wang Setting [~guozhang] as the reviewer. This change is needed in order to complet

[jira] [Commented] (KAFKA-2631) Expose data volume via JMX

[ https://issues.apache.org/jira/browse/KAFKA-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953242#comment-14953242 ] Eno Thereska commented on KAFKA-2631: - It turns out we already have a Meter that measu

Re: [DISCUSS] KIP-37 - Add namespaces in Kafka

Ashish, Thank you for doing this writeup and starting the discussion around namespaces and multi-tenancy. We have implemented a namespace solution on top of Kafka trunk and our motivation to do so matches your description in KIP-37 to a large extent. But there are some differences in our approach

Kafka-no such method exception - custom partitioner

i follow the tutorial on https://cwiki.apache.org/confluence/display/KAFKA/0.8.0+Producer+Example, but got the following error exception in thread "main" java.lang.ClassNotFoundException: example.producer.SimplePartitioner at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLCl

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953062#comment-14953062 ] Ismael Juma commented on KAFKA-1804: Note that the code in trunk looks different and t

[jira] [Comment Edited] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953030#comment-14953030 ] Vladimir Picka edited comment on KAFKA-1804 at 10/12/15 11:54 AM: --

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953030#comment-14953030 ] Vladimir Picka commented on KAFKA-1804: --- Hello, I just would like to report that thi

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952925#comment-14952925 ] Tom Lee commented on KAFKA-2063: This sounds familiar. Am I right in thinking something si

[jira] [Commented] (KAFKA-2565) Offset Commit is not working if multiple consumers try to commit the offset

[ https://issues.apache.org/jira/browse/KAFKA-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952795#comment-14952795 ] Sreenivasulu Nallapati commented on KAFKA-2565: --- This happens basically in t