You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Edward Sargisson (JIRA)" <ji...@apache.org> on 2013/04/08 17:53:16 UTC

[jira] [Commented] (FLUME-1971) Log4jAppender that uses an Embedded Agent internally

    [ https://issues.apache.org/jira/browse/FLUME-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625477#comment-13625477 ] 

Edward Sargisson commented on FLUME-1971:
-----------------------------------------

Note that the Log4j2 project has a Flume Appender which can either be an embedded agent or merely connect directly. We have recently found some issues with its handling of a disconnected successor agent however:

* LOG4J2-196 log4j2 blocks on logging calls if the FlumeAppender loses its connection to the remote flume agent
* LOG4J2-197 log4j2 creates 2 threads per each log attempt if the remote flume agent goes down
* LOG4J2-198 log4j2 stops application from shutting down if the FlumeAppender is being used


                
> Log4jAppender that uses an Embedded Agent internally
> ----------------------------------------------------
>
>                 Key: FLUME-1971
>                 URL: https://issues.apache.org/jira/browse/FLUME-1971
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira