You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/02 02:33:00 UTC

[jira] [Updated] (HBASE-18046) replace 'hbase.client.log.scanner.activity' with logger

     [ https://issues.apache.org/jira/browse/HBASE-18046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-18046:
--------------------------
    Fix Version/s:     (was: 1.5.0)
                       (was: 3.0.0)
                       (was: 2.0.0)

> 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
>
> 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
(v7.6.3#76005)