You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/04/17 23:45:25 UTC

[jira] [Commented] (ACCUMULO-2343) Create Appender specifically for log-forwarding

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

Christopher Tubbs commented on ACCUMULO-2343:
---------------------------------------------

This ticket is marked for 1.6.1. I think it's probably best if these changes do not get introduced until the next feature release and not in 1.6.1, especially since full implementation will change the behavior of the logging initialization, and simply making it available means that any utilization of it would require incompatible changes to logging configuration that couldn't work with 1.6.0.

> Create Appender specifically for log-forwarding
> -----------------------------------------------
>
>                 Key: ACCUMULO-2343
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2343
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor, tserver
>            Reporter: Josh Elser
>            Assignee: Bill Havanki
>            Priority: Minor
>             Fix For: 1.6.1, 1.7.0
>
>
> Currently, the log4j configuration defines an AsyncAppender which wraps a SocketAppender. It would likely be cleaner, and easy to track, if we created our own AccumuloMonitorAppender (or similar).
> This would make disabling log-forwarding when the monitor is dead easier to accomplish. It might also allow for reuse of this functionality.



--
This message was sent by Atlassian JIRA
(v6.2#6252)