[
https://issues.apache.org/jira/browse/KAFKA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184729#comment-13184729
]
Stefano Santoro commented on KAFKA-244:
---------------------------------------
I opted for configuration flexibility by assigning an option specification
priority: zk.connecf, broker.list, and host/port pair (which is then translated
into broker.list) If more then one is specified, then the one with the highest
priority is picked. What I was hoping for though is that you wold help me
understand why specifying broker.list works, but specifying zk.connect hangs.
> Improve log4j appender to use kafka.producer.Producer, and support
> zk.connect|broker.list options
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-244
> URL: https://issues.apache.org/jira/browse/KAFKA-244
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.7.1
> Reporter: Stefano Santoro
> Labels: log4j, newbie
> Fix For: 0.7.1
>
> Attachments: Log4jAppender.patch
>
>
> Taken from #kafka IRC session with Neha Narkhede:
> The log4j appender is quite obsolete, there are a few things to change there.
> Make it use the kafka.producer.Producer instead of SyncProducer. That allows
> you to use either the broker.list or the zk.connect option
--
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
