[jira] [Commented] (KAFKA-550) Wildcarded consumption is single-threaded

[ https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472158#comment-13472158 ] Jun Rao commented on KAFKA-550: --- Thanks for the patch. What was the bug? Is it the implicit f

[jira] [Commented] (KAFKA-548) remove partition from ProducerRequestPartitionData and FetchResponsePartitionData

[ https://issues.apache.org/jira/browse/KAFKA-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472147#comment-13472147 ] Joel Koshy commented on KAFKA-548: -- Why is it dirty? :) It looks pretty good to me - I did

[jira] [Commented] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472145#comment-13472145 ] Jun Rao commented on KAFKA-510: --- Patch doesn't seem to apply to 0.8. The text leading up to

[jira] [Resolved] (KAFKA-539) Replica.hw should be initialized to the smaller of checkedpointed HW and log end offset

[ https://issues.apache.org/jira/browse/KAFKA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-539. --- Resolution: Fixed Fix Version/s: 0.8 Thanks for the patch. Committed to 0.8. > Replica

[jira] [Closed] (KAFKA-539) Replica.hw should be initialized to the smaller of checkedpointed HW and log end offset

[ https://issues.apache.org/jira/browse/KAFKA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-539. - > Replica.hw should be initialized to the smaller of checkedpointed HW and log > end offset > ---

[jira] [Commented] (KAFKA-551) Log.truncateTo() may need to trucate immutable log segment

[ https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472133#comment-13472133 ] Jun Rao commented on KAFKA-551: --- Thanks for the patch. Looks good. Just one comment. 1. Offs

[jira] [Commented] (KAFKA-432) allow consumer to read from followers

[ https://issues.apache.org/jira/browse/KAFKA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472126#comment-13472126 ] Jun Rao commented on KAFKA-432: --- Patch no longer applies. Could you rebase?

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472123#comment-13472123 ] Jun Rao commented on KAFKA-42: -- Also, could you make the two new scripts in bin/ executable?

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472121#comment-13472121 ] Jun Rao commented on KAFKA-42: -- Thanks for patch v4. AdminTest.testResumePartitionReassignment

Re: [ANN] node.js lib for kafka

thanks for sending it around always great to know different client options they could go in the 0.7 section of non-java clients https://cwiki.apache.org/confluence/display/KAFKA/Kafka+non-java+clients if you want to update the page too On Mon, Oct 8, 2012 at 10:43 PM, Taylor Gautier wrote: > At

[jira] [Updated] (KAFKA-548) remove partition from ProducerRequestPartitionData and FetchResponsePartitionData

[ https://issues.apache.org/jira/browse/KAFKA-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-548: -- Attachment: kafka_548_v1.diff It's dirty but it does work > remove partition from ProducerReq

Re: [ANN] node.js lib for kafka

At Tagged, I wrote the following: https://github.com/tagged/node-kafka It's been in production since January. Probably we should merge the two projects so that there is a canonical implementation. It doesn't support any zookeeper stuff - just provides a consumer and a producer. On Mon, Oct 8,

[jira] [Updated] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-42: --- Attachment: kafka-42-v4.patch > Support rebalancing the partitions with replication > -

[jira] [Updated] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-42: --- Attachment: (was: kafka-42-v4.patch) > Support rebalancing the partitions with replication > --

[ANN] node.js lib for kafka

I'm not sure if you are interested in hearing about library support from other languages, but I thought I'd let you know about this: https://github.com/cainus/Prozess / https://npmjs.org/package/prozess There are lots of TODOs still on this, but we've got a Kafka lib working in node.js that han

[jira] [Commented] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471964#comment-13471964 ] John Fung commented on KAFKA-502: - Uploaded kafka-502-v8.patch to change the following case

[jira] [Updated] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-502: Attachment: kafka-502-v8.patch > Simplify setup / initialization in replication_basic_test.py >

[jira] [Closed] (KAFKA-549) ConsumerOffsetChecker does not deal with hostnames published in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy closed KAFKA-549. > ConsumerOffsetChecker does not deal with hostnames published in zookeeper > --

[jira] [Updated] (KAFKA-549) ConsumerOffsetChecker does not deal with hostnames published in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-549: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed. > ConsumerO

[jira] [Updated] (KAFKA-550) Wildcarded consumption is single-threaded

[ https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-550: - Attachment: KAFKA-550-v1.patch This was a silly coding bug - the topicThreadIdAndQueues map was getting up

[jira] [Updated] (KAFKA-550) Wildcarded consumption is single-threaded

[ https://issues.apache.org/jira/browse/KAFKA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-550: - Status: Patch Available (was: Open) > Wildcarded consumption is single-threaded > ---

[jira] [Updated] (KAFKA-551) Log.truncateTo() may need to trucate immutable log segment

[ https://issues.apache.org/jira/browse/KAFKA-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-551: Attachment: KAFKA-551.patch Attached patch removes mutable flag from offset index and log file. I think thi

[jira] [Commented] (KAFKA-552) No error messages logged for those failing-to-send messages from Producer

[ https://issues.apache.org/jira/browse/KAFKA-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471930#comment-13471930 ] John Fung commented on KAFKA-552: - * Attached the following files for reference: File 1: s

[jira] [Updated] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-42: --- Attachment: kafka-42-v4.patch 20.3 Good point, I see what you are saying. Fixed it > S

[jira] [Updated] (KAFKA-552) No error messages logged for those failing-to-send messages from Producer

[ https://issues.apache.org/jira/browse/KAFKA-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-552: Attachment: testcase_0123_logs.tar.gz testcase_0122_logs.tar.gz system_test_o

[jira] [Created] (KAFKA-552) No error messages logged for those failing-to-send messages from Producer

John Fung created KAFKA-552: --- Summary: No error messages logged for those failing-to-send messages from Producer Key: KAFKA-552 URL: https://issues.apache.org/jira/browse/KAFKA-552 Project: Kafka

[jira] [Reopened] (KAFKA-517) Ensure that we escape the metric names if they include user strings

[ https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy reopened KAFKA-517: -- I think it is better to fix this properly - i.e., although topics could cause this (before we had the topic

[jira] [Commented] (KAFKA-517) Ensure that we escape the metric names if they include user strings

[ https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471879#comment-13471879 ] Yang Ye commented on KAFKA-517: --- This is resolved by imposing constrains on the topic names

[jira] [Resolved] (KAFKA-517) Ensure that we escape the metric names if they include user strings

[ https://issues.apache.org/jira/browse/KAFKA-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye resolved KAFKA-517. --- Resolution: Fixed > Ensure that we escape the metric names if they include user strings >

[jira] [Commented] (KAFKA-516) Consider catching all exceptions in ShutdownableThread

[ https://issues.apache.org/jira/browse/KAFKA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471872#comment-13471872 ] Yang Ye commented on KAFKA-516: --- In ShutdownableThread , all exceptions are actually caught.

[jira] [Resolved] (KAFKA-516) Consider catching all exceptions in ShutdownableThread

[ https://issues.apache.org/jira/browse/KAFKA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye resolved KAFKA-516. --- Resolution: Fixed > Consider catching all exceptions in ShutdownableThread > -

[jira] [Updated] (KAFKA-539) Replica.hw should be initialized to the smaller of checkedpointed HW and log end offset

[ https://issues.apache.org/jira/browse/KAFKA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-539: -- Attachment: kafka_539_v1.diff I only find one place to patch > Replica.hw should be initialize

[jira] [Updated] (KAFKA-510) broker needs to know the replication factor per partition

[ https://issues.apache.org/jira/browse/KAFKA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-510: -- Attachment: kafka_510_v5.diff Rebase from Jay's patch > broker needs to know the replication f

Re: [jira] [Resolved] (KAFKA-506) Store logical offset in log

Hi Taylor, These are good questions. 1. It is required. It seemed cleaner to have one mechanism for mapping the "log change number" to the physical message and make that efficient rather than have lots of options. 2. Zero-copy transfer is still used. The performance impact can be understood in t

Re: [jira] [Resolved] (KAFKA-506) Store logical offset in log

I seem to be late to the party on this one - can you summarize what happened to the log files - and wire protocol - as a result of this change? I have some questions regarding what implications this change has: 1) is it required or optional, iotw can the physical offset mechanism still be used? 2

[jira] [Resolved] (KAFKA-504) UnsatisfiedLinkError causes snappy unit tests to fail on hudson server

[ https://issues.apache.org/jira/browse/KAFKA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-504. - Resolution: Fixed Assignee: Jay Kreps Included in KAFKA-506 > UnsatisfiedLinkError

[jira] [Resolved] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-506. - Resolution: Fixed Committed. > Store logical offset in log > ---

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (61 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-549 ConsumerOffsetChecker does not deal with hostnames published in zookeeper https://issues.apache.org/jira/browse

[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository

[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471741#comment-13471741 ] Chris Aniszczyk commented on KAFKA-133: --- bump... +1 Can this be done? We're looking

[jira] [Comment Edited] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471720#comment-13471720 ] John Fung edited comment on KAFKA-502 at 10/8/12 6:28 PM: -- Thanks

[jira] [Commented] (KAFKA-42) Support rebalancing the partitions with replication

[ https://issues.apache.org/jira/browse/KAFKA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471733#comment-13471733 ] Jun Rao commented on KAFKA-42: -- Thanks for patch v3. Looks good to me overall. Just one comment

[jira] [Commented] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471720#comment-13471720 ] John Fung commented on KAFKA-502: - Thanks Jun for reviewing. Uploaded kafka-502-v7.patch wi

[jira] [Updated] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-502: Attachment: kafka-502-v7.patch > Simplify setup / initialization in replication_basic_test.py >

[jira] [Commented] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471698#comment-13471698 ] Jun Rao commented on KAFKA-506: --- +1 from me. > Store logical offset in log >

[jira] [Commented] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471637#comment-13471637 ] Jay Kreps commented on KAFKA-506: - Should apply on HEAD. > Store logical o

[jira] [Commented] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471631#comment-13471631 ] Neha Narkhede commented on KAFKA-506: - Btw, which svn revision does patch v5 apply corr

[jira] [Commented] (KAFKA-506) Store logical offset in log

[ https://issues.apache.org/jira/browse/KAFKA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471628#comment-13471628 ] Neha Narkhede commented on KAFKA-506: - Agree that rebasing is painful. In addition to m

[jira] [Commented] (KAFKA-502) Simplify setup / initialization in replication_basic_test.py

[ https://issues.apache.org/jira/browse/KAFKA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471616#comment-13471616 ] Jun Rao commented on KAFKA-502: --- Thanks for patch v6. A few more comments: 60. Most of the n

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (61 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-549 ConsumerOffsetChecker does not deal with hostnames published in zookeeper https://issues.apache.org/jira/browse