[
https://issues.apache.org/jira/browse/HBASE-18046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009500#comment-16009500
]
Sean Busbey commented on HBASE-18046:
-------------------------------------
It'd be nice if we issued a warning with pointers if someone still set
'hbase.client.log.scanner.activity' after we stop relying on it.
> replace 'hbase.client.log.scanner.activity' with logger
> -------------------------------------------------------
>
> Key: HBASE-18046
> URL: https://issues.apache.org/jira/browse/HBASE-18046
> Project: HBase
> Issue Type: Improvement
> Components: Operability
> Affects Versions: 0.94.0, 0.98.0, 1.0.0, 2.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0
> Reporter: Sean Busbey
> Priority: Minor
> Fix For: 2.0.0, 1.5.0
>
>
> HBASE-6004 introduced some additional INFO logging around scanners that's
> critical to debugging. Because of the additional logging
> it guarded that activity behind a new config
> 'hbase.client.log.scanner.activity'.
> There's a comment in the reviews that it'd be more consistent to handle this
> via a different logger or a different logging level.
> This jira is to complete that work, so that operators trying to debug scans
> can just rely on configuring the logging framework without having to also set
> a client config.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
