You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2009/04/29 07:27:33 UTC

[jira] Resolved: (CHUKWA-68) Race condition could stop log file streaming

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

Eric Yang resolved CHUKWA-68.
-----------------------------

    Resolution: Duplicate

This is most likely a duplicate of Chukwa-159.  Close this as duplicate.

> Race condition could stop log file streaming
> --------------------------------------------
>
>                 Key: CHUKWA-68
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-68
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection
>         Environment: Redhat 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>
> When log file is actively writing with log4j appender, and fileTailingAdaptor is behind.  There is a possibility that restart the java program might stop log file streaming.
> Here is an example of what could go wrong:
> 04:01 Shutdown Name Node.
> 04:01 Terminator Thread kick in and streaming the remaining log.
> 04:02 Name Node Started up
> 04:03 Register of namenode log file failed because it is already streaming.
> 04:20 Terminator Thread finished the log file, unregister name node log for streaming.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.