[jira] [Commented] (KAFKA-593) Empty log index file created when it shouldn't be empty

[ https://issues.apache.org/jira/browse/KAFKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487841#comment-13487841 ] Jun Rao commented on KAFKA-593: --- Here is the issue. We rolled a new segment in the follower.

[jira] [Closed] (KAFKA-594) Update System Test due to new argument --sync in ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-594. - Update System Test due to new argument --sync in ProducerPerformance

[jira] [Updated] (KAFKA-586) system test configs are broken

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

[jira] [Closed] (KAFKA-586) system test configs are broken

[ https://issues.apache.org/jira/browse/KAFKA-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-586. - system test configs are broken -- Key: KAFKA-586

[jira] [Commented] (KAFKA-593) Empty log index file created when it shouldn't be empty

[ https://issues.apache.org/jira/browse/KAFKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487878#comment-13487878 ] Jay Kreps commented on KAFKA-593: - Makes sense, clever. I thought a bit about this during

[jira] [Commented] (KAFKA-593) Empty log index file created when it shouldn't be empty

[ https://issues.apache.org/jira/browse/KAFKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487879#comment-13487879 ] Jay Kreps commented on KAFKA-593: - Err, that should read intra-messageset positions.

[jira] [Commented] (KAFKA-595) Producer side compression is unnecessary

[ https://issues.apache.org/jira/browse/KAFKA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487915#comment-13487915 ] Neha Narkhede commented on KAFKA-595: - I would recommend we instead add a

[jira] [Updated] (KAFKA-595) Producer side compression is unnecessary

[ https://issues.apache.org/jira/browse/KAFKA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-595: Issue Type: Improvement (was: Bug) Producer side compression is unnecessary

[jira] [Created] (KAFKA-596) LogSegment.firstAppendTime not reset after truncate to

Jun Rao created KAFKA-596: - Summary: LogSegment.firstAppendTime not reset after truncate to Key: KAFKA-596 URL: https://issues.apache.org/jira/browse/KAFKA-596 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-596) LogSegment.firstAppendTime not reset after truncate to

[ https://issues.apache.org/jira/browse/KAFKA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487947#comment-13487947 ] Jun Rao commented on KAFKA-596: --- The fix is to set LogSegment.firstAppendTime to none if we

[jira] [Updated] (KAFKA-188) Support multiple data directories

[ https://issues.apache.org/jira/browse/KAFKA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-188: Attachment: KAFKA-188-v8.patch This failing test was due to a real bug in LogManager.shutdown that lead to

[jira] [Created] (KAFKA-597) Refactor KafkaScheduler

Jay Kreps created KAFKA-597: --- Summary: Refactor KafkaScheduler Key: KAFKA-597 URL: https://issues.apache.org/jira/browse/KAFKA-597 Project: Kafka Issue Type: Bug Affects Versions: 0.8.1

[jira] [Commented] (KAFKA-513) Add state change log to Kafka brokers

[ https://issues.apache.org/jira/browse/KAFKA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13488162#comment-13488162 ] Neha Narkhede commented on KAFKA-513: - Prashanth, how is the work on this going, do you

[jira] [Resolved] (KAFKA-590) System Test - 4 cases failed due to insufficient no. of retry in ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung resolved KAFKA-590. - Resolution: Fixed These 4 test cases are passing after setting producer-retry-backoff-ms to 2500 which

[jira] [Closed] (KAFKA-590) System Test - 4 cases failed due to insufficient no. of retry in ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung closed KAFKA-590. --- System Test - 4 cases failed due to insufficient no. of retry in ProducerPerformance

[jira] [Updated] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-532: Status: In Progress (was: Patch Available) Multiple controllers can co-exist during soft

[jira] [Updated] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-532: Attachment: kafka-532-v3.patch So we don't need to rewrite leaderAndIsr during controller

[jira] [Commented] (KAFKA-545) Add a Performance Suite for the Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13488366#comment-13488366 ] Jay Kreps commented on KAFKA-545: - The initial set of results show the following: Big

[jira] [Updated] (KAFKA-574) KafkaController unnecessarily reads leaderAndIsr info from ZK

[ https://issues.apache.org/jira/browse/KAFKA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashanth Menon updated KAFKA-574: -- Attachment: KAFKA-574-v2.patch I've attached a new patched rebased against 0.8 head which