[jira] [Updated] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-736: Attachment: check-message-ordering.py We have the producer performance that can take in an option to

[jira] [Commented] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569320#comment-13569320 ] ben fleis commented on KAFKA-736: - This is more-or-less what my node command line tool does

[jira] [Commented] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569304#comment-13569304 ] Jay Kreps commented on KAFKA-736: - It would be nice to have an "ordering" torture test. The

[jira] [Commented] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569294#comment-13569294 ] ben fleis commented on KAFKA-736: - Went back and tested the 'draft' patch, and this failed

[jira] [Updated] (KAFKA-671) DelayedProduce requests should not hold full producer request data

[ https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-671: Status: Patch Available (was: Open) > DelayedProduce requests should not hold full producer req

[jira] [Commented] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569224#comment-13569224 ] Jay Kreps commented on KAFKA-736: - Reviewing the draft patch in case we end up going that r

[jira] [Closed] (KAFKA-713) Update Hadoop producer for Kafka 0.8 changes

[ https://issues.apache.org/jira/browse/KAFKA-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-713. --- > Update Hadoop producer for Kafka 0.8 changes > > >

[jira] [Updated] (KAFKA-713) Update Hadoop producer for Kafka 0.8 changes

[ https://issues.apache.org/jira/browse/KAFKA-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-713: Resolution: Fixed Fix Version/s: (was: 0.8.1) 0.8 Status: Re

[jira] [Commented] (KAFKA-713) Update Hadoop producer for Kafka 0.8 changes

[ https://issues.apache.org/jira/browse/KAFKA-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568962#comment-13568962 ] Neha Narkhede commented on KAFKA-713: - +1 > Update Hadoop producer for

[jira] [Commented] (KAFKA-695) Broker shuts down due to attempt to read a closed index file

[ https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568927#comment-13568927 ] Neha Narkhede commented on KAFKA-695: - Thanks for the follow up patch, most of the chan

[jira] [Assigned] (KAFKA-747) RequestChannel re-design

[ https://issues.apache.org/jira/browse/KAFKA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede reassigned KAFKA-747: --- Assignee: Neha Narkhede > RequestChannel re-design > > >

[jira] [Commented] (KAFKA-747) RequestChannel re-design

[ https://issues.apache.org/jira/browse/KAFKA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568911#comment-13568911 ] Sriram Subramanian commented on KAFKA-747: -- I proposed a similar solution but slig

[jira] [Updated] (KAFKA-747) RequestChannel re-design

[ https://issues.apache.org/jira/browse/KAFKA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-747: Component/s: network > RequestChannel re-design > > > Key: KAFK

[jira] [Created] (KAFKA-747) RequestChannel re-design

Jay Kreps created KAFKA-747: --- Summary: RequestChannel re-design Key: KAFKA-747 URL: https://issues.apache.org/jira/browse/KAFKA-747 Project: Kafka Issue Type: New Feature Reporter: Jay

[jira] [Comment Edited] (KAFKA-734) Migration tool needs a revamp, it was poorly written and has many performance bugs

[ https://issues.apache.org/jira/browse/KAFKA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568900#comment-13568900 ] Neha Narkhede edited comment on KAFKA-734 at 2/1/13 5:33 PM: - -

[jira] [Updated] (KAFKA-734) Migration tool needs a revamp, it was poorly written and has many performance bugs

[ https://issues.apache.org/jira/browse/KAFKA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-734: Attachment: kafka-734-v3.patch - KafkaMigrationTool Simplified the partitioning logic of the produc