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] [Updated] (HADOOP-7556) TaskLogAppender does not check if closed before flushing
Date Fri, 19 Aug 2011 04:09:27 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron Morton updated HADOOP-7556:
---------------------------------

    Attachment: HADDOP-7556.diff

Patch to check if the TaskLogAppender is closed before flushing.

> 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: 0.20.203.0
>            Reporter: Aaron Morton
>            Priority: Minor
>         Attachments: HADDOP-7556.diff
>
>
> For background see http://groups.google.com/group/brisk-users/browse_thread/thread/3a18f4679673bea8
> http://mail-archives.apache.org/mod_mbox/hadoop-common-user/201108.mbox/%3C4E370C97-1541-4FDA-8456-1067DDDC4D77@thelastpickle.com%3E
> 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

        

Mime
View raw message