[jira] [Reopened] (ACCUMULO-4409) Create a custom log4j AccumuloMonitorAppender

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

     [ https://issues.apache.org/jira/browse/ACCUMULO-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser reopened ACCUMULO-4409:
----------------------------------

{noformat}
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.272 sec <<< FAILURE! - in org.apache.accumulo.monitor.util.AccumuloMonitorAppenderTest
testMonitorTracker(org.apache.accumulo.monitor.util.AccumuloMonitorAppenderTest)  Time elapsed: 0.121 sec  <<< ERROR!
java.util.NoSuchElementException: Vector Enumeration
	at org.apache.accumulo.monitor.util.AccumuloMonitorAppenderTest.verifyAppender(AccumuloMonitorAppenderTest.java:177)
	at org.apache.accumulo.monitor.util.AccumuloMonitorAppenderTest.updateLocAndVerify(AccumuloMonitorAppenderTest.java:166)
	at org.apache.accumulo.monitor.util.AccumuloMonitorAppenderTest.testMonitorTracker(AccumuloMonitorAppenderTest.java:149)
{noformat}

{noformat}
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
Maven home: /usr/local/Cellar/maven/3.5.0/libexec
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
{noformat}

[~ctubbsii] this test failed for me on Master. Could you please look into it?

> Create a custom log4j AccumuloMonitorAppender
> ---------------------------------------------
>
>                 Key: ACCUMULO-4409
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4409
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>              Labels: release_notes
>             Fix For: 2.0.0
>
>          Time Spent: 6h
>  Remaining Estimate: 0h
>
> The current AsyncSocketAppender was an improvement over the older log4j configuration options, but it did not fully satisfy the description in ACCUMULO-2343.
> What we really need is an appender which can be managed by configuration alone, without using code to reload it with new system properties when the location of the monitor changes.
> So, rather than having a ZK watcher reload the log4j system, the appender itself should internally detect the relocation of the monitor and adjust its behavior accordingly. That way, the configuration files do not need to refer to system properties for the hostname/port of the monitor, and there is no need to reload the log4j logging when things change.
> This will allow us to remove more custom log4j code, which gets us closer to users having the ability to use another implementation for the slf4j API (though this feature of logging to the monitor might not be available for other slf4j implementations, unless they support using log4j appenders).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)