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

["Cheng (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CHUKWA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696293#action_12696293 ] 

Cheng edited comment on CHUKWA-68 at 4/6/09 4:18 PM:
-----------------------------------------------------

I stopped and restarted name node couple times. From the list 
command, I can see the adaptor was removed and added back and forth.
Waited for 10 minutes, did not find any problem. 

      was (Author: zhangyongjiang):
    I stopped and restarted name node gs301033 couple times. From the list 
command, I can see the adaptor was removed and added back and forth.
Waited for 10 minutes, did not find any problem. 
  
> 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
>            Priority: Blocker
>
> 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.