[
https://issues.apache.org/jira/browse/HBASE-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549793#comment-14549793
]
Hudson commented on HBASE-13675:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6491 (See
[https://builds.apache.org/job/HBase-TRUNK/6491/])
HBASE-13675 ProcedureExecutor completion report should be at DEBUG log level
(ssrungarapu: rev 901714d75dd6da9c3b7dca3f48046119c6f08905)
*
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/ProcedureExecutor.java
> ProcedureExecutor completion report should be at DEBUG log level
> ----------------------------------------------------------------
>
> Key: HBASE-13675
> URL: https://issues.apache.org/jira/browse/HBASE-13675
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Andrew Purtell
> Assignee: Srikanth Srungarapu
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.1.1
>
> Attachments: HBASE-13675.patch, HBASE-13675_v2.patch
>
>
> Example:
> {noformat}
> 2015-05-12 12:05:03,445 INFO [ProcedureExecutorThread-0]
> procedure2.ProcedureExecutor: Procedure completed in 838msec:
> EnableTableProcedure (table=cluster_test) user=apurtell (auth:SIMPLE) id=5
> state=FINISHED
> {noformat}
> The procedures themselves are already emitting task specific information at
> INFO level. This doesn't add much information besides the elapsed time, so
> probably should be at DEBUG level. I assume if a procedure fails there will
> be additional logging at WARN level, but if not, that could be a
> consideration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
