Yes, presently our logging infrastructure doesn't work well with
"standard" log4j configuration (I think we have a ticket floating around
somewhere, but I don't recall the ID off the top of my head).
If your concern is only with using a properties configuration file
instead of XML, ACCUMULO-2383 introduced the means to do so. For the
time being, you'll have to use generic_logger.(xml|properties) as a way
to configure log4j. You can also create specific
*_logger.(xml|properties) to configure certain components if necessary
(e.g. tserver_logger.xml or master_logger.xml).
Denis wrote:
Well, that depends on what is in -Dlog4j.configuration=
If there is an URI
(-Dlog4j.configuration=file:/path/to/log4j.configuration) as log4j
expects, Accumulo stops file-based logging as soon as it starts log
forwarding.
If there is a path
(-Dlog4j.configuration=/path/to/log4j.configuration) then Accumulo is
happy but log4j blames "Please initialize the log4j system properly"
and file-based logging does not start until log forwarding is enabled.
It is better not to use -Dlog4j.configuration at all but those
tservers are running with
-Dlog4j.configuration=file:/path/to/log4j.configuration :(
On 1/13/15, Josh Elser<[email protected]> wrote:
Denis wrote:
Do you have any warnings/errors in the new server's logs?
On smaller cluster where I try to reproduce the problem - no
On big cluster, unfortunately, there are no local logs as the tserver
logs were sent to the monitor:(
At the moment I cannot add a new tserver there to collect new logs as
clients are using the cluster.
Huh? Log-forwarding to the monitor doesn't preclude local file-based
logging. You can have both.
