You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Srikanth Srungarapu (JIRA)" <ji...@apache.org> on 2015/05/18 05:12:59 UTC
[jira] [Updated] (HBASE-13675) ProcedureExecutor completion report
should be at DEBUG log level
[ https://issues.apache.org/jira/browse/HBASE-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srikanth Srungarapu updated HBASE-13675:
----------------------------------------
Attachment: HBASE-13675.patch
Changed the log level to DEBUG besides some minor nits.
> 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
> Attachments: HBASE-13675.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)