[jira] [Closed] (KAFKA-907) controller needs to close socket channel to brokers on exception

[ https://issues.apache.org/jira/browse/KAFKA-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-907. --- > controller needs to close socket channel to brokers on exception > -

Re: produce request wire format question

1. Correct 2. The producer does not use or depend on zookeeper anymore. It refreshes its view of the cluster metadata by using a TopicMetadataRequest to any of the kafka brokers. It maps a message to a partition using the following rules - 2.1 If a message has no key, use any available partition 2.

[jira] [Closed] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

[ https://issues.apache.org/jira/browse/KAFKA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy closed KAFKA-914. > Deadlock between initial rebalance and watcher-triggered rebalances >

[jira] [Resolved] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

[ https://issues.apache.org/jira/browse/KAFKA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-914. -- Resolution: Fixed Thanks for the review. Committed after removing the unnecessary assignment in MirrorM

[jira] [Updated] (KAFKA-907) controller needs to close socket channel to brokers on exception

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

[jira] [Created] (KAFKA-916) Deadlock between fetcher shutdown and handling partitions with error

Joel Koshy created KAFKA-916: Summary: Deadlock between fetcher shutdown and handling partitions with error Key: KAFKA-916 URL: https://issues.apache.org/jira/browse/KAFKA-916 Project: Kafka Iss

[jira] [Commented] (KAFKA-915) System Test - Mirror Maker testcase_5001 failed

[ https://issues.apache.org/jira/browse/KAFKA-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664653#comment-13664653 ] John Fung commented on KAFKA-915: - This issue is not reproducible in the following commit (

[jira] [Updated] (KAFKA-915) System Test - Mirror Maker testcase_5001 failed

[ https://issues.apache.org/jira/browse/KAFKA-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-915: Attachment: testcase_5001_debug_logs.tar.gz > System Test - Mirror Maker testcase_5001 failed >

[jira] [Created] (KAFKA-915) System Test - Mirror Maker testcase_5001 failed

John Fung created KAFKA-915: --- Summary: System Test - Mirror Maker testcase_5001 failed Key: KAFKA-915 URL: https://issues.apache.org/jira/browse/KAFKA-915 Project: Kafka Issue Type: Bug

Re: produce request wire format question

Ok, the picture I have in my mind of how things work in 0.8 (from a producer's point of view) is as follows: 1. An application program sends log messages to a producer. Each message is provided as a key/value pair, where the key is chosen by the application and the value is t

[jira] [Commented] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

[ https://issues.apache.org/jira/browse/KAFKA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664474#comment-13664474 ] Neha Narkhede commented on KAFKA-914: - Thanks for the patch! Good catch, +1

[jira] [Commented] (KAFKA-907) controller needs to close socket channel to brokers on exception

[ https://issues.apache.org/jira/browse/KAFKA-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664298#comment-13664298 ] Neha Narkhede commented on KAFKA-907: - Thanks for the patch. The following if statement

[jira] [Commented] (KAFKA-911) Bug in controlled shutdown logic in controller leads to controller not sending out some state change request

[ https://issues.apache.org/jira/browse/KAFKA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664277#comment-13664277 ] Neha Narkhede commented on KAFKA-911: - testShutdownBroker() testcase in AdminTest will

[jira] [Updated] (KAFKA-911) Bug in controlled shutdown logic in controller leads to controller not sending out some state change request

[ https://issues.apache.org/jira/browse/KAFKA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-911: Status: Patch Available (was: In Progress) > Bug in controlled shutdown logic in controller lea

https://issues.apache.org/jira/browse/KAFKA-259

Hi, I have created a patch for this issue. Can you pls. review and let me know? Thanks for all your help. Ashwanth

[jira] [Updated] (KAFKA-911) Bug in controlled shutdown logic in controller leads to controller not sending out some state change request

[ https://issues.apache.org/jira/browse/KAFKA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-911: Attachment: kafka-911-v1.patch The root cause of this bug was a race condition while using the Cont

[jira] [Work started] (KAFKA-911) Bug in controlled shutdown logic in controller leads to controller not sending out some state change request

[ https://issues.apache.org/jira/browse/KAFKA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-911 started by Neha Narkhede. > Bug in controlled shutdown logic in controller leads to controller not > sending out some state change request > --

Re: produce request wire format question

Dave, Currently, the broker expects each producer request to specify the exact partition id (-1 is on longer valid). The mapping from a message to a partition is done at the producer client. The producer can choose a random partition (from the existing list of partitions) or deterministically choo