-[jira] [Updated] (KAFKA-524) Kafka Appender causes Log4j Deadlock
"Jun Rao 2013-02-14, 18:03
[ https://issues.apache.org/jira/browse/KAFKA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-524:
Assignee: David Arthur
Status: Resolved (was: Patch Available)
Thanks for patch v2. Committed to 0.7 branch.
In 0.8, the producer issus metadata requests to the brokers to figure out the leader of each partition. So, the producer doesn't need to know ZK. Instead, it needs to know a subset of brokers. One can also use a VIP in front of the brokers.
> Kafka Appender causes Log4j Deadlock
> Key: KAFKA-524
> URL: https://issues.apache.org/jira/browse/KAFKA-524
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 0.7.2
> Reporter: nicu marasoiu
> Assignee: David Arthur
> Labels: patch
> Fix For: 0.7.2
> Attachments: 0001-KAFKA-524-Defer-creating-Producer-in-log4j-appender.patch, 0001-KAFKA-524-Defer-creating-Producer-in-log4j-appender.patch
> If you remove all log4j.properties from classpath (and prvent any log4j intialization previous to the one which involves kafka appender), and put KAFKA appender on rootLogger, then, even if you exclude the KAFKA appender from logger.kafka and logger.org, you get a Log4j deadlock when zookeeper send thread tries to issue a LOG.info, and for that it locks the root category (as its correct category, say org, is not yet set up in log4j, who is still in activateOptions on kafka appender).
> please read comments on the parent and ask any questions to [EMAIL PROTECTED]
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira