[
https://issues.apache.org/jira/browse/KAFKA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162922#comment-13162922
]
Jun Rao commented on KAFKA-197:
-------------------------------
The main reason that we moved away from writing to local log is to pick up the
compression support in the high level producer. Decoupling the embedded
consumer from the broker may not be a bad idea. There is one more
service/process that one has to manage. However, it's probably more flexible
(to support things like consuming from multiple sources and plugging in logic
for consumer-side auditing) and is less intrusive to the core Kafka code.
> Embedded consumer doesn't shut down if the server can't start
> -------------------------------------------------------------
>
> Key: KAFKA-197
> URL: https://issues.apache.org/jira/browse/KAFKA-197
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.7
> Reporter: Jun Rao
> Fix For: 0.7.1
>
> Attachments: KAFKA-197.patch
>
>
> If a broker embeds a consumer and the broker itself doesn't start (e.g.,
> conflicting broker id in ZK), the embedded consumer is still running. In this
> case, we should probably shut down the embedded consumer too.
> To do this, we need to either throw an exception or return an error in
> KafkaServer.startup and act accordingly in KafkaServerStartable.startup.
--
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
