[
https://issues.apache.org/jira/browse/CHUKWA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695839#action_12695839
]
Ari Rabkin commented on CHUKWA-68:
----------------------------------
Suppose the namenode never tried to unregister the log -- would that solve the
problem? Seems like that's actually the right behavior. The cost of having
Chukwa continue watching the file is pretty low.
> 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
> Environment: Redhat 5.1, Java 6
> Reporter: 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.
