[
https://issues.apache.org/jira/browse/HBASE-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-3017.
--------------------------
Assignee: stack
Fix Version/s: 0.90.0
Resolution: Fixed
Committed
{code}
M conf/log4j.properties
Make ZKW log at INFO-level
M src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
Log message cleanup.
M src/main/java/org/apache/hadoop/hbase/master/HMaster.java
Remove excessive hostname+port qualifier on master for zk messages
M src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
Log message cleanup
M src/main/java/org/apache/hadoop/hbase/master/ServerManager.java
Format the ServerMonitor message.
M src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
Remove excessive hostname on zk message id; just add port
M src/main/java/org/apache/hadoop/hbase/zookeeper/ZKAssign.java
Cleanup of messages.
{code}
> More log pruning
> ----------------
>
> Key: HBASE-3017
> URL: https://issues.apache.org/jira/browse/HBASE-3017
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.90.0
>
>
> This issue covers some tightening up of log messages; as is all of the zk
> noise tends to overwhelm.
> For example, zkwatcher logs a generic "This event happened in zk with path X
> and event type Y" but just after, there will be a log from the handler of
> this zk event with this subsequent log more descriptive. This change would
> make zkwatcher log at INFO by default rather than DEBUG cutting down on
> logging content (re-enabling DEBUG is easy to do if needed).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
