You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "David Medinets (JIRA)" <ji...@apache.org> on 2012/07/14 15:06:33 UTC
[jira] [Created] (ACCUMULO-692) Display hostname and port in DEBUG
level log messages when unable to connect.
David Medinets created ACCUMULO-692:
---------------------------------------
Summary: Display hostname and port in DEBUG level log messages when unable to connect.
Key: ACCUMULO-692
URL: https://issues.apache.org/jira/browse/ACCUMULO-692
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (ACCUMULO-692) Display hostname and port in
DEBUG level log messages when unable to connect.
Posted by David Medinets <da...@gmail.com>.
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.
[jira] [Updated] (ACCUMULO-692) Display hostname and port in DEBUG
level log messages when unable to connect.
Posted by "Christopher Tubbs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-692:
---------------------------------------
Affects Version/s: (was: 1.5.0)
> Display hostname and port in DEBUG level log messages when unable to connect.
> -----------------------------------------------------------------------------
>
> Key: ACCUMULO-692
> URL: https://issues.apache.org/jira/browse/ACCUMULO-692
> Project: Accumulo
> Issue Type: Improvement
> Reporter: David Medinets
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ACCUMULO-692) Display hostname and port in DEBUG
level log messages when unable to connect.
Posted by "Christopher Tubbs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs reassigned ACCUMULO-692:
------------------------------------------
Assignee: Christopher Tubbs
> Display hostname and port in DEBUG level log messages when unable to connect.
> -----------------------------------------------------------------------------
>
> Key: ACCUMULO-692
> URL: https://issues.apache.org/jira/browse/ACCUMULO-692
> Project: Accumulo
> Issue Type: Improvement
> Reporter: David Medinets
> Assignee: Christopher Tubbs
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-692) Display hostname and port in
DEBUG level log messages when unable to connect.
Posted by "Josh Elser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414477#comment-13414477 ]
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: https://issues.apache.org/jira/browse/ACCUMULO-692
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACCUMULO-692) Display hostname and port in
DEBUG level log messages when unable to connect.
Posted by "Josh Elser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414464#comment-13414464 ]
Josh Elser commented on ACCUMULO-692:
-------------------------------------
IMO, if I were running a production instance, I'd probably want to know when an Accumulo service isn't running. You could get this same information from the monitor page, but I'd assume that production instances would have some sort of log-scraping service to automatically alert you when such a process isn't running.
> Display hostname and port in DEBUG level log messages when unable to connect.
> -----------------------------------------------------------------------------
>
> Key: ACCUMULO-692
> URL: https://issues.apache.org/jira/browse/ACCUMULO-692
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACCUMULO-692) Display hostname and port in DEBUG
level log messages when unable to connect.
Posted by "Christopher Tubbs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-692:
---------------------------------------
Fix Version/s: 1.5.0
> Display hostname and port in DEBUG level log messages when unable to connect.
> -----------------------------------------------------------------------------
>
> Key: ACCUMULO-692
> URL: https://issues.apache.org/jira/browse/ACCUMULO-692
> Project: Accumulo
> Issue Type: Improvement
> Reporter: David Medinets
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira