[
https://issues.apache.org/jira/browse/FLUME-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424570#comment-13424570
]
Jarek Jarcec Cecho commented on FLUME-1400:
-------------------------------------------
Hi Patrik,
there is already available some weak documentation for the tail in the user
guide http://flume.apache.org/FlumeUserGuide.html#exec-source
I'm definitely open to the idea of extending it, so please do your
investigation and put together notes. I'll more than happy to review them :-)
Jarcec
> Understand and document behavior of exec source when tailing rolling logs
> -------------------------------------------------------------------------
>
> Key: FLUME-1400
> URL: https://issues.apache.org/jira/browse/FLUME-1400
> Project: Flume
> Issue Type: Improvement
> Reporter: Patrick Wendell
> Assignee: Patrick Wendell
>
> There has been some discussion recently around the behavior of exec("tail
> -f") when tailing logs, if the log files are themselves being rolled and
> renamed by a writer process.
> The primary concern is whether there is a race condition or correctness
> problem related to tailing a log which is renamed.
> I am fairly certain that the tail binary, when passed -f, will deal with all
> of the ugliness of recognizing when a file is rolled and open the new
> "current" file as expected. However, we should both verify and document that
> behavior.
> Flume OG, which implemented its own tailing functionality, dealt with this
> ugliness by introducing increasing break-fix complexity to the tail source. I
> am hoping that by delegating to the "tail" binary we have avoided having to
> do this (though at the cost of OS portability). Nonetheless, I should confirm
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
