[
https://issues.apache.org/jira/browse/KAFKA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-350:
--------------------------------
Attachment: kafka-350-v4.patch
21. Not really. updateInfo() is not the only API that throws
NoBrokersForPartitionException. partitionAndCollate can encounter that
exception while calling the getPartitionListForTopic() API. But you raised a
good point here. What partitionAndCollate() should do (given its current
design) is to log a retry warning for recoverable exceptions and return None,
so that they are included in the retry. For non-recoverable exceptions, it
should just throw the exception to the handle API and mark it failed.
30. Added an error message for non-positive values for request timeout. Al
though a value of zero means infinite timeout
31. I guess so. Changed it back to IllegalStateException
32. Removed socket timeout related stuff from ProducerPerformance
33. Removed the import.
34. Hmm, that can happen if you try to create a topic when the brokers haven't
yet registered in zookeeper. The system tests waits for 2 seconds, which should
be enough for couple of brokers to startup in the normal case. I haven't been
able to reproduce this. Its possible that this is something that can be fixed
in the system test. File a bug if you see it.
> Enable message replication in the presence of controlled failures
> -----------------------------------------------------------------
>
> Key: KAFKA-350
> URL: https://issues.apache.org/jira/browse/KAFKA-350
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Attachments: kafka-350-v1.patch, kafka-350-v2.patch,
> kafka-350-v3.patch, kafka-350-v4.patch
>
>
> KAFKA-46 introduced message replication feature in the absence of server
> failures. This JIRA will improve the log recovery logic and fix other bugs to
> enable message replication to happen in the presence of controlled server
> failures
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
