accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-692) Display hostname and port in DEBUG level log messages when unable to connect.
Date Sat, 14 Jul 2012 19:14:33 GMT


Josh Elser commented on ACCUMULO-692:

??In production, I'd expect usage of nagios or similar monitoring tool. Displaying the hostname
and port in debugging messages helps the novice during the configuration stage. Also in production,
I'd expect the various connections to be well documented in an operations manual.??

Oops, I misinterpreted your request, my apologies. Read your post to user@accumulo. I'm not
sure I buy hostnames as being so sensitive as to keep them out of production log files (if
someone has access to your logs, they probably have the ability to netstat and make a pretty
good guess about things).

tl;dr Adding hostname:port to exception stacktraces would be good, not sure I agree with only
putting them at DEBUG. The security argument seems excessive to me. +1 to Corey Nolt's statement
about Hadoop/ZooKeeper also placing similar messages at INFO (follow existing Hadoop conventions).
> Display hostname and port in DEBUG level log messages when unable to connect.
> -----------------------------------------------------------------------------
>                 Key: ACCUMULO-692
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.5.0
>            Reporter: David Medinets
>            Priority: Minor
> As I configured Accumulo, I saw messages like the following in the logs. In would be
helpful if the hostname and port of the destination were displayed as DEBUG message in the
logs. The DEBUG level is used so that security-minded people can set log4j to just show INFO
level or higher in production.
> 13 01... Unable to contact the garbage collector
> org.apache...ConnectException: Connection refused

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message