[jira] [Updated] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-521: Attachment: KAFKA-521-v5.patch New patch. Addresses your comments (see below) and also one more refactoring

[jira] [Commented] (KAFKA-635) Producer error when trying to send not displayed unless in DEBUG logging level

[ https://issues.apache.org/jira/browse/KAFKA-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505222#comment-13505222 ] Jun Rao commented on KAFKA-635: --- Chris, Thanks for reporting this. Do you really nee

[jira] [Created] (KAFKA-636) Make log segment delete asynchronous

Jay Kreps created KAFKA-636: --- Summary: Make log segment delete asynchronous Key: KAFKA-636 URL: https://issues.apache.org/jira/browse/KAFKA-636 Project: Kafka Issue Type: Bug Reporter

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505183#comment-13505183 ] Neha Narkhede commented on KAFKA-521: - Pretty good cleanup and great usage of

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505148#comment-13505148 ] Swapnil Ghike commented on KAFKA-521: - Log.deleteOldSegments: Just a nitpic

[jira] [Updated] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-622: Attachment: kafka-622-v3.patch 1. I see your point, that's good to know. Now using a case

[jira] [Updated] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-521: Attachment: KAFKA-521-v4.patch New patch, v4, contains two changes: 1. Remove unused imports Swapnil

[jira] [Commented] (KAFKA-633) AdminTest.testShutdownBroker fails

[ https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505095#comment-13505095 ] Jay Kreps commented on KAFKA-633: - Another annoying thing is that after AdminTest runs

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504871#comment-13504871 ] Swapnil Ghike commented on KAFKA-521: - 1. I see, thanks for the clarification

[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=13504826#comment-13504826 ] Jay Kreps commented on KAFKA-133: - Hey Otis, that's awesome. Thanks for taking

[jira] [Created] (KAFKA-635) Producer error when trying to send not displayed unless in DEBUG logging level

Chris Curtin created KAFKA-635: -- Summary: Producer error when trying to send not displayed unless in DEBUG logging level Key: KAFKA-635 URL: https://issues.apache.org/jira/browse/KAFKA-635 Project

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504815#comment-13504815 ] Jay Kreps commented on KAFKA-521: - 1. The point of the logic is to recompress all

[jira] [Created] (KAFKA-634) ConsoleProducer compresses messages and ignores the --compress flag

Paul Garner created KAFKA-634: - Summary: ConsoleProducer compresses messages and ignores the --compress flag Key: KAFKA-634 URL: https://issues.apache.org/jira/browse/KAFKA-634 Project: Kafka

[jira] [Commented] (KAFKA-260) Add audit trail to kafka

[ https://issues.apache.org/jira/browse/KAFKA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504487#comment-13504487 ] Lorenz Knies commented on KAFKA-260: Hi, i like option 2. I wrote a generic cons

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504392#comment-13504392 ] Swapnil Ghike commented on KAFKA-521: - Overall, a lot of things have become much

[jira] [Created] (KAFKA-633) AdminTest.testShutdownBroker fails

Jun Rao created KAFKA-633: - Summary: AdminTest.testShutdownBroker fails Key: KAFKA-633 URL: https://issues.apache.org/jira/browse/KAFKA-633 Project: Kafka Issue Type: Bug Components: core

[jira] [Created] (KAFKA-632) ProducerRequest should take ByteBufferMessageSet instead of MessageSet

Jun Rao created KAFKA-632: - Summary: ProducerRequest should take ByteBufferMessageSet instead of MessageSet Key: KAFKA-632 URL: https://issues.apache.org/jira/browse/KAFKA-632 Project: Kafka Issue

[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=13504367#comment-13504367 ] Otis Gospodnetic commented on KAFKA-133: Update on the zklient front -

[jira] [Updated] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-521: Attachment: KAFKA-521-v3.patch Updated patch. Only change is to make the maxOffset parameter in Log.read

[jira] [Commented] (KAFKA-631) Implement log compaction

[ https://issues.apache.org/jira/browse/KAFKA-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504192#comment-13504192 ] Jay Kreps commented on KAFKA-631: - Here is a specific proposal: We will retain

[jira] [Created] (KAFKA-631) Implement log compaction

Jay Kreps created KAFKA-631: --- Summary: Implement log compaction Key: KAFKA-631 URL: https://issues.apache.org/jira/browse/KAFKA-631 Project: Kafka Issue Type: New Feature Components

[jira] [Resolved] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-544. - Resolution: Fixed > Retain key in producer and expose it in the consu

[jira] [Commented] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504066#comment-13504066 ] Jay Kreps commented on KAFKA-521: - This patch is ready for review. It is intended

[jira] [Updated] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-521: Attachment: KAFKA-521-v2.patch Updated patch. In addition to the items in v1 This has the following changes

[jira] [Commented] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504003#comment-13504003 ] Joel Koshy commented on KAFKA-544: -- +1 - although can you fix the typo? *

[jira] Subscription: outstanding kafka patches

/jira/browse/KAFKA-628 KAFKA-622 Create mbeans per client https://issues.apache.org/jira/browse/KAFKA-622 KAFKA-621 System Test 9051 : ConsoleConsumer doesn't receives any data for 20 topics but works for 10 https://issues.apache.org/jira/browse/KAFKA-621 KAFK

[jira] [Commented] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503464#comment-13503464 ] Eli Reisman commented on KAFKA-544: --- I like it! > Retain

[jira] [Resolved] (KAFKA-344) migration tool from 0.7 to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-344. - Resolution: Fixed Yes, this is done now > migration tool from 0.7 to

[jira] [Closed] (KAFKA-344) migration tool from 0.7 to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-344. --- > migration tool from 0.7 to 0.8 > -- > > Ke

[jira] [Commented] (KAFKA-344) migration tool from 0.7 to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502950#comment-13502950 ] Jay Kreps commented on KAFKA-344: - This is done now, right? > mi

[jira] [Commented] (KAFKA-468) String#getBytes is platform dependent

[ https://issues.apache.org/jira/browse/KAFKA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502947#comment-13502947 ] Jay Kreps commented on KAFKA-468: - I integrated the changes in KAFKA-367 into the p

[jira] [Updated] (KAFKA-468) String#getBytes is platform dependent

[ https://issues.apache.org/jira/browse/KAFKA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-468: Resolution: Fixed Status: Resolved (was: Patch Available) > String#getBytes is platf

[jira] [Commented] (KAFKA-367) StringEncoder/StringDecoder use platform default character set

[ https://issues.apache.org/jira/browse/KAFKA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502946#comment-13502946 ] Jay Kreps commented on KAFKA-367: - Eli, I was also working on the same area for KAFKA

[jira] [Updated] (KAFKA-367) StringEncoder/StringDecoder use platform default character set

[ https://issues.apache.org/jira/browse/KAFKA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-367: Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available

[jira] [Resolved] (KAFKA-562) Non-failure System Test Log Segment File Checksums mismatched

[ https://issues.apache.org/jira/browse/KAFKA-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-562. - Resolution: Fixed Fix Version/s: 0.8 This was addressed a while back. >

[jira] Subscription: outstanding kafka patches

/jira/browse/KAFKA-628 KAFKA-622 Create mbeans per client https://issues.apache.org/jira/browse/KAFKA-622 KAFKA-621 System Test 9051 : ConsoleConsumer doesn't receives any data for 20 topics but works for 10 https://issues.apache.org/jira/browse/KAFKA-621 KAFK

[jira] [Commented] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502889#comment-13502889 ] Neha Narkhede commented on KAFKA-622: - Thanks for incorporating suggestions in

[jira] [Updated] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-544: Attachment: KAFKA-544-joel-comments-v2.patch Nice catches, fixed. > Retain key in produ

[jira] [Commented] (KAFKA-430) Improve the "waitUntilLeaderIsElectedOrChanged" function in TestUtils class

[ https://issues.apache.org/jira/browse/KAFKA-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502464#comment-13502464 ] Jim Plush commented on KAFKA-430: - What are you planning on improving? Any details ar

[jira] [Commented] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502310#comment-13502310 ] Joel Koshy commented on KAFKA-544: -- Thanks a lot for addressing the above. Changes

[jira] [Updated] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-544: Attachment: KAFKA-544-joel-comments.patch Hey Joel, those are good points. Here is a follow-up patch that

[jira] [Updated] (KAFKA-521) Refactor Log subsystem

[ https://issues.apache.org/jira/browse/KAFKA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-521: Attachment: KAFKA-521-v1.patch Changes FileMessageSet: - Improve docs - rename constructor argument

[jira] [Updated] (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:all-tabpanel ] Neha Narkhede updated KAFKA-133: Fix Version/s: 0.8 > Publish kafka jar to a public maven reposit

[jira] [Updated] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-622: Attachment: kafka-622-v2.patch 1.2, 2.1, 3.2, 5.3, 9.2: Renamed *Stat to *Stats and get*Stat to

[jira] [Updated] (KAFKA-630) Auto create topic doesn't reflect the new topic and throws UnknownTopicOrPartitionException

[ https://issues.apache.org/jira/browse/KAFKA-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-630: Affects Version/s: 0.8 > Auto create topic doesn't reflect the new topic an

[jira] [Created] (KAFKA-630) Auto create topic doesn't reflect the new topic and throws UnknownTopicOrPartitionException

Neha Narkhede created KAFKA-630: --- Summary: Auto create topic doesn't reflect the new topic and throws UnknownTopicOrPartitionException Key: KAFKA-630 URL: https://issues.apache.org/jira/browse/KAFK

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (56 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-622 Create mbeans per client https://issues.apache.org/jira/browse/KAFKA-622 KAFKA-621 System Test 9051

[jira] [Updated] (KAFKA-608) getTopicMetadata does not respect producer config settings

[ https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-608: Priority: Blocker (was: Major) Affects Version/s: 0.8 Fix Version/s: 0.8

[jira] [Commented] (KAFKA-626) Produce requests dropped due to socket timeouts on get metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500441#comment-13500441 ] Jay Kreps commented on KAFKA-626: - Suspect the root cause is KAFKA-608. I am changing

[jira] [Commented] (KAFKA-626) Produce requests dropped due to socket timeouts on get metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500427#comment-13500427 ] Neha Narkhede commented on KAFKA-626: - nnarkhed-ld:apache-kafka-0.8 nnarkhed$

[jira] [Commented] (KAFKA-627) Make UnknownTopicOrPartitionException a WARN in broker

[ https://issues.apache.org/jira/browse/KAFKA-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500426#comment-13500426 ] Jay Kreps commented on KAFKA-627: - Since this is expected behavior it seems like

[jira] [Created] (KAFKA-627) Make UnknownTopicOrPartitionException a WARN in broker

Chris Riccomini created KAFKA-627: - Summary: Make UnknownTopicOrPartitionException a WARN in broker Key: KAFKA-627 URL: https://issues.apache.org/jira/browse/KAFKA-627 Project: Kafka Issue

[jira] [Created] (KAFKA-626) Produce requests dropped due to socket timeouts on get metadata requests

Neha Narkhede created KAFKA-626: --- Summary: Produce requests dropped due to socket timeouts on get metadata requests Key: KAFKA-626 URL: https://issues.apache.org/jira/browse/KAFKA-626 Project: Kafka

[jira] [Closed] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-612. - > move shutting down of fetcher thread out of critical p

[jira] [Updated] (KAFKA-612) move shutting down of fetcher thread out of critical path

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

[jira] [Commented] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499956#comment-13499956 ] Neha Narkhede commented on KAFKA-612: - Minor nitpick before you checkin v2 - Pl

[jira] [Updated] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-612: -- Attachment: kafka-612-v2.patch Thanks for the review. Attach patch v2. 1.1 This is to handle the case that a

[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-tabpanel&focusedCommentId=13499949#comment-13499949 ] Neha Narkhede commented on KAFKA-513: - Swapnil, I think this JIRA is missing

[jira] [Resolved] (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 resolved KAFKA-532. - Resolution: Fixed 50. Agree that the request/response formats must be consistent. Let's

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13499941#comment-13499941 ] Jun Rao commented on KAFKA-532: --- 50. My feeling is that request level error code conveys

[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=13499940#comment-13499940 ] Neha Narkhede commented on KAFKA-133: - * How come this is not Fix Version 0.8? Sh

[jira] [Updated] (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:all-tabpanel ] Neha Narkhede updated KAFKA-133: Affects Version/s: 0.8 > Publish kafka jar to a public maven reposit

[jira] [Commented] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499938#comment-13499938 ] Neha Narkhede commented on KAFKA-544: - Minor comment - The API docs are broke

[jira] [Closed] (KAFKA-625) Improve MessageAndMetadata to expose the partition

[ https://issues.apache.org/jira/browse/KAFKA-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-625. --- > Improve MessageAndMetadata to expose the partit

[jira] [Resolved] (KAFKA-625) Improve MessageAndMetadata to expose the partition

[ https://issues.apache.org/jira/browse/KAFKA-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-625. - Resolution: Duplicate Fix Version/s: 0.8 Fixed as part of KAFKA-544

[jira] [Updated] (KAFKA-616) Implement acks=0

[ https://issues.apache.org/jira/browse/KAFKA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-616: Affects Version/s: 0.8 > Implement acks=0 > > > Ke

[jira] [Created] (KAFKA-625) Improve MessageAndMetadata to expose the partition

Neha Narkhede created KAFKA-625: --- Summary: Improve MessageAndMetadata to expose the partition Key: KAFKA-625 URL: https://issues.apache.org/jira/browse/KAFKA-625 Project: Kafka Issue Type

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13499873#comment-13499873 ] Neha Narkhede commented on KAFKA-532: - Thanks for reviewing patch v5 quickly !

[jira] [Commented] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499861#comment-13499861 ] Neha Narkhede commented on KAFKA-622: - 1. AbstractFetcherThread 1.1 Maybe the clie

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13499860#comment-13499860 ] Jun Rao commented on KAFKA-532: --- Thanks for patch v5. Looks good. Just a couple of m

[jira] [Commented] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499572#comment-13499572 ] Neha Narkhede commented on KAFKA-612: - Overall, the fix looks good, here are a

[jira] [Comment Edited] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499572#comment-13499572 ] Neha Narkhede edited comment on KAFKA-612 at 11/18/12 1:0

[jira] [Commented] (KAFKA-620) UnknownHostError looking for a ZK node crashes the broker

[ https://issues.apache.org/jira/browse/KAFKA-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499561#comment-13499561 ] Neha Narkhede commented on KAFKA-620: - I would check if the zookeeper connec

[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-v5.patch ew more changes in this patch - 1. Changed leader and isr request

[jira] [Updated] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-622: Attachment: kafka-622-v1.patch The major change in this patch is to convert a bunch of *Stat

[jira] [Resolved] (KAFKA-618) Deadlock between leader-finder-thread and consumer-fetcher-thread during broker failure

[ https://issues.apache.org/jira/browse/KAFKA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-618. -- Resolution: Fixed > Deadlock between leader-finder-thread and consumer-fetcher-thread dur

[jira] [Closed] (KAFKA-618) Deadlock between leader-finder-thread and consumer-fetcher-thread during broker failure

[ https://issues.apache.org/jira/browse/KAFKA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy closed KAFKA-618. Committed to 0.8 > Deadlock between leader-finder-thread and consumer-fetcher-thread dur

[jira] [Resolved] (KAFKA-613) MigrationTool should disable shallow iteration in the 0.7 consumer

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

[jira] [Closed] (KAFKA-613) MigrationTool should disable shallow iteration in the 0.7 consumer

[ https://issues.apache.org/jira/browse/KAFKA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-613. - > MigrationTool should disable shallow iteration in the 0.7 consu

[jira] [Commented] (KAFKA-618) Deadlock between leader-finder-thread and consumer-fetcher-thread during broker failure

[ https://issues.apache.org/jira/browse/KAFKA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499309#comment-13499309 ] Jun Rao commented on KAFKA-618: --- Thanks for the patch. +1 > D

[jira] [Updated] (KAFKA-613) MigrationTool should disable shallow iteration in the 0.7 consumer

[ https://issues.apache.org/jira/browse/KAFKA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-613: -- Attachment: kafka_613_v2.patch add logging > MigrationTool should disable shallow iterat

[jira] [Updated] (KAFKA-618) Deadlock between leader-finder-thread and consumer-fetcher-thread during broker failure

[ https://issues.apache.org/jira/browse/KAFKA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-618: - Attachment: KAFKA-618-v1.patch Ran 20 iterations of testcase 4011 and they all pass. One potential

[jira] [Resolved] (KAFKA-614) DumpLogSegment offset verification is incorrect for compressed messages

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

[jira] [Closed] (KAFKA-614) DumpLogSegment offset verification is incorrect for compressed messages

[ https://issues.apache.org/jira/browse/KAFKA-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-614. - > DumpLogSegment offset verification is incorrect for compressed messa

[jira] [Assigned] (KAFKA-624) Add 07 ConsoleConsumer to validate message content for Migration Tool testcases

[ https://issues.apache.org/jira/browse/KAFKA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung reassigned KAFKA-624: --- Assignee: John Fung > Add 07 ConsoleConsumer to validate message content for Migration T

[jira] [Created] (KAFKA-624) Add 07 ConsoleConsumer to validate message content for Migration Tool testcases

John Fung created KAFKA-624: --- Summary: Add 07 ConsoleConsumer to validate message content for Migration Tool testcases Key: KAFKA-624 URL: https://issues.apache.org/jira/browse/KAFKA-624 Project: Kafka

[jira] [Commented] (KAFKA-613) MigrationTool should disable shallow iteration in the 0.7 consumer

[ https://issues.apache.org/jira/browse/KAFKA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499269#comment-13499269 ] Jun Rao commented on KAFKA-613: --- Thanks for patch v1. It would be good to also log a war

[jira] [Updated] (KAFKA-614) DumpLogSegment offset verification is incorrect for compressed messages

[ https://issues.apache.org/jira/browse/KAFKA-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-614: -- Attachment: kafka_614_v1.patch kafka_614_v1.patch > DumpLogSegment offset verification

[jira] [Updated] (KAFKA-614) DumpLogSegment offset verification is incorrect for compressed messages

[ https://issues.apache.org/jira/browse/KAFKA-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-614: -- Attachment: (was: kafka_614_v1.patch) > DumpLogSegment offset verification is incorrect for compres

[jira] [Updated] (KAFKA-613) MigrationTool should disable shallow iteration in the 0.7 consumer

[ https://issues.apache.org/jira/browse/KAFKA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye updated KAFKA-613: -- Attachment: kafka_613_v1.patch disable shallow iteration > MigrationTool should disa

[jira] [Commented] (KAFKA-609) System Test Transient Failure 9001 (Migration tool) - ConsoleConsumer terminates after "can't rebalance after 4 retries"

[ https://issues.apache.org/jira/browse/KAFKA-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499235#comment-13499235 ] Yang Ye commented on KAFKA-609: --- We found this is not a real issue. The reason is si

[jira] [Resolved] (KAFKA-609) System Test Transient Failure 9001 (Migration tool) - ConsoleConsumer terminates after "can't rebalance after 4 retries"

[ https://issues.apache.org/jira/browse/KAFKA-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Ye resolved KAFKA-609. --- Resolution: Fixed > System Test Transient Failure 9001 (Migration tool) - ConsoleConsumer > term

[jira] [Created] (KAFKA-623) It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector

Jason Rosenberg created KAFKA-623: - Summary: It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector Key: KAFKA-623 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (KAFKA-619) Regression : System Test 900x (Migration Tool) - java.lang.ClassCastException: kafka.message.Message cannot be cast to [B

[ https://issues.apache.org/jira/browse/KAFKA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-619. - Resolution: Fixed > Regression : System Test 900x (Migration Tool) - > java.lang.ClassCastExc

[jira] [Commented] (KAFKA-619) Regression : System Test 900x (Migration Tool) - java.lang.ClassCastException: kafka.message.Message cannot be cast to [B

[ https://issues.apache.org/jira/browse/KAFKA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499175#comment-13499175 ] Jay Kreps commented on KAFKA-619: - I believe I have fixed

[jira] [Created] (KAFKA-622) Create mbeans per client

Swapnil Ghike created KAFKA-622: --- Summary: Create mbeans per client Key: KAFKA-622 URL: https://issues.apache.org/jira/browse/KAFKA-622 Project: Kafka Issue Type: Bug Components

[jira] [Updated] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Ghike updated KAFKA-622: Labels: bugs improvement (was: improvement) > Create mbeans per cli

[jira] [Commented] (KAFKA-620) UnknownHostError looking for a ZK node crashes the broker

[ https://issues.apache.org/jira/browse/KAFKA-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499043#comment-13499043 ] Jun Rao commented on KAFKA-620: --- Do you have other ZK hosts in your connection st

[jira] [Updated] (KAFKA-605) System Test - Log Retention Cases should wait longer before getting the common starting offset in replica log segments

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

[jira] [Closed] (KAFKA-605) System Test - Log Retention Cases should wait longer before getting the common starting offset in replica log segments

[ https://issues.apache.org/jira/browse/KAFKA-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-605. - > System Test - Log Retention Cases should wait longer before getting the > common starting offset in r

  1   2   3   4   5   6   7   8   9   10   >