hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Morton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-7556) TaskLogAppender does not check if closed before flushing
Date Fri, 19 Aug 2011 03:08:29 GMT
TaskLogAppender does not check if closed before flushing

                 Key: HADOOP-7556
                 URL: https://issues.apache.org/jira/browse/HADOOP-7556
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions:
            Reporter: Aaron Morton
            Priority: Minor

For background see http://groups.google.com/group/brisk-users/browse_thread/thread/3a18f4679673bea8

Cassandra is using a log4j PropertyConfigurator which is closing all existing appenders. After
a task has completed the TaskLogAppender.flush() is called and it tries to flush without checking
if the writer has been closed. I'll upload a patch to check if the writer is closed, and log
and silently fail if it is. 

The real problem is the log4j config collision, we're looking to different log4j LoggerRepositories
for that. 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message