Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)

I am closing the vote, the vote passes at least three PPMC binding votes and I will send an vote request to the get two more IPMC votes (Chris being a member of the IPMC, right?) I say at least three as I am not sure if Joel's vote is binding or not. Let me know so I when I vote. On Wed, Oct 3, 2

Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)

Joe, >From https://incubator.apache.org/guides/releasemanagement.html#rules, the rules are: Each release requires a positive vote binding on Apache. This means a . There is usually no need for this vote to be private. (A rare exception might be a -1 due to a nearly discovered security issue, for

Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)

Thanks Jun but for binding they have to be member of PPMC and IPMC and those are not documented anywhere I could find, that was my question is if Joel's vote is binding now... it would be upon graduating as would mine but was not sure what the rules were now, more for my own edification than anyth

Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)

Joe, Yes, Joel's vote is not binding, but Chris (IPMC), Neha (PPMC) and mine (PPMC) are. Thanks, Jun On Wed, Oct 3, 2012 at 8:29 AM, Joe Stein wrote: > Thanks Jun but for binding they have to be member of PPMC and IPMC and > those are not documented anywhere I could find, that was my question

[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=13468644#comment-13468644 ] Jun Rao commented on KAFKA-506: --- There is another issue: 45. ConsumerIterator: Now that we i

Re: Producer code

I think you mean DefaultEventHandler. Yes, kafka-409 has been created for that. Thanks, Jun On Tue, Oct 2, 2012 at 4:50 PM, Jay Kreps wrote: > Hey Guys, > > The code in the Producer has gotten very dense and spaghetti-like. I see a > lot of types like > Map[TopicAndPartition, Seq[ProducerDat

Re: Incubator PMC/Board report for Oct 2012 ([ppmc])

Apparently, this is due today. I put together a draft at http://wiki.apache.org/incubator/October2012 Alan, can you sign-off if it looks good to you? Thanks, Joel On Tue, Oct 2, 2012 at 12:11 PM, Marvin wrote: > > > Dear podling, > > This email was sent by an automated system on behalf of the

[jira] [Commented] (KAFKA-363) Replace numerical compression codes in config with something human readable

[ https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468772#comment-13468772 ] Joel Koshy commented on KAFKA-363: -- +1 (I don't think we need to apply this to trunk.) Com

[jira] [Updated] (KAFKA-363) Replace numerical compression codes in config with something human readable

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

[jira] [Closed] (KAFKA-363) Replace numerical compression codes in config with something human readable

[ https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy closed KAFKA-363. > Replace numerical compression codes in config with something human readable >

[jira] [Updated] (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 updated KAFKA-506: Attachment: KAFKA-506-v4-changes-since-v3.patch KAFKA-506-phase-2-v4.patch Here is a new pat

[jira] [Commented] (KAFKA-508) split out partiondata from fetchresponse and producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468825#comment-13468825 ] Jun Rao commented on KAFKA-508: --- Hi, Joe, Do you still plan to work on this jira? Thanks,

[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=13468863#comment-13468863 ] Joel Koshy commented on KAFKA-510: -- Thanks for patch v1. I have a few comments: 1 - Condi

[jira] [Commented] (KAFKA-508) split out partiondata from fetchresponse and producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468865#comment-13468865 ] Joe Stein commented on KAFKA-508: - yes, sorry been swamped at work. looking at where i l

[jira] [Comment Edited] (KAFKA-508) split out partiondata from fetchresponse and producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468865#comment-13468865 ] Joe Stein edited comment on KAFKA-508 at 10/4/12 8:39 AM: -- yes, so

[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=13468896#comment-13468896 ] Jun Rao commented on KAFKA-506: --- Patch v4 looks good overall. A couple of remaining issues:

[jira] [Created] (KAFKA-540) log.append() should halt on IOException

Jun Rao created KAFKA-540: - Summary: log.append() should halt on IOException Key: KAFKA-540 URL: https://issues.apache.org/jira/browse/KAFKA-540 Project: Kafka Issue Type: Bug Components: c

[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=13468947#comment-13468947 ] Jun Rao commented on KAFKA-42: -- Thanks for patch v2. Some more comments: 20. ReassignPartition

[jira] [Updated] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-540: -- Fix Version/s: 0.8 Status: Patch Available (was: Open) > log.append() should halt on IOException

[jira] [Updated] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-540: -- Attachment: kafka-540.patch Attach a patch to fix the issue. > log.append() should halt on IOEx

[jira] [Assigned] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-540: - Assignee: Jun Rao > log.append() should halt on IOException > ---

[jira] [Created] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

Joel Koshy created KAFKA-541: Summary: Use metrics CSV reporter instead of jmx tool for system tests Key: KAFKA-541 URL: https://issues.apache.org/jira/browse/KAFKA-541 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469012#comment-13469012 ] Jay Kreps commented on KAFKA-540: - This is a good change--calling exit in the lower level c

[jira] [Commented] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

[ https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469015#comment-13469015 ] Joel Koshy commented on KAFKA-541: -- Some sample output: https://gist.github.com/3830723

[jira] [Updated] (KAFKA-508) split out partiondata from fetchresponse and producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-508: Attachment: KAFKA-508.patch > split out partiondata from fetchresponse and producerrequest > ---

[jira] [Updated] (KAFKA-508) split out partiondata from fetchresponse and producerrequest

[ https://issues.apache.org/jira/browse/KAFKA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-508: Status: Patch Available (was: Open) > split out partiondata from fetchresponse and producerrequest > --

[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=13469034#comment-13469034 ] Jun Rao commented on KAFKA-432: --- Thanks for patch v2. A few other minor comments: 10. FetchR

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

[ https://issues.apache.org/jira/browse/KAFKA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-432: -- Attachment: kafka_432_v3.diff addressed all comments for v2 patch > allow consumer to read fro

[jira] [Commented] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

[ https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469043#comment-13469043 ] Joel Koshy commented on KAFKA-541: -- Actually, now I remember. metrics 3.0.0 fixes this iss

[jira] [Created] (KAFKA-542) Upgrade to metrics 3.x

Joel Koshy created KAFKA-542: Summary: Upgrade to metrics 3.x Key: KAFKA-542 URL: https://issues.apache.org/jira/browse/KAFKA-542 Project: Kafka Issue Type: Bug Affects Versions: 0.8

[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_v2.diff Joel, Thanks for comment, new patch uploaded > broker needs to

[jira] [Assigned] (KAFKA-267) Enhance ProducerPerformance to generate unique random Long value for payload

[ https://issues.apache.org/jira/browse/KAFKA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye reassigned KAFKA-267: - Assignee: Yang Ye (was: John Fung) > Enhance ProducerPerformance to generate unique random Long value

[jira] [Updated] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-540: -- Attachment: kafka-540_v2.patch Attach patch v2. 1. changed to KafkaStorageException. 2. I think we should call

[jira] [Commented] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

[ https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469061#comment-13469061 ] Joel Koshy commented on KAFKA-541: -- Also, FYI, here are the configs to add to a server to

[jira] [Updated] (KAFKA-542) Upgrade to metrics 3.x

[ https://issues.apache.org/jira/browse/KAFKA-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-542: - Attachment: KAFKA-542-v1.patch Patch overview: 1 - I sent a mail to metrics-user group asking when 3.0.0

[jira] [Commented] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469068#comment-13469068 ] Jay Kreps commented on KAFKA-540: - +1 > log.append() should halt on IOExce

[jira] [Commented] (KAFKA-541) Use metrics CSV reporter instead of jmx tool for system tests

[ https://issues.apache.org/jira/browse/KAFKA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469104#comment-13469104 ] Neha Narkhede commented on KAFKA-541: - +1, this will be great to have. Also, even with

[jira] [Created] (KAFKA-543) Something is wrong with the metadata request in DefaultEventHandler.handle

Jay Kreps created KAFKA-543: --- Summary: Something is wrong with the metadata request in DefaultEventHandler.handle Key: KAFKA-543 URL: https://issues.apache.org/jira/browse/KAFKA-543 Project: Kafka

[jira] [Updated] (KAFKA-543) Metadata request from DefaultEventHandler.handle repeats same topic over and over

[ https://issues.apache.org/jira/browse/KAFKA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-543: Summary: Metadata request from DefaultEventHandler.handle repeats same topic over and over (was: Something

[jira] [Updated] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-540: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the review. Committed 0.8.

[jira] [Closed] (KAFKA-540) log.append() should halt on IOException

[ https://issues.apache.org/jira/browse/KAFKA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-540. - > log.append() should halt on IOException > --- > > Key: KAFKA