Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C4450200C76 for ; Sat, 13 May 2017 21:56:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C2CD9160BBB; Sat, 13 May 2017 19:56:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15BD1160BB2 for ; Sat, 13 May 2017 21:56:08 +0200 (CEST) Received: (qmail 27048 invoked by uid 500); 13 May 2017 19:56:08 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 27037 invoked by uid 99); 13 May 2017 19:56:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 May 2017 19:56:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CA037C002B for ; Sat, 13 May 2017 19:56:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 74S0Q8P9r5Wk for ; Sat, 13 May 2017 19:56:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 69A8C5FC72 for ; Sat, 13 May 2017 19:56:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C8E5CE0A75 for ; Sat, 13 May 2017 19:56:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1682C242F5 for ; Sat, 13 May 2017 19:56:04 +0000 (UTC) Date: Sat, 13 May 2017 19:56:04 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18046) replace 'hbase.client.log.scanner.activity' with logger MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 13 May 2017 19:56:10 -0000 [ 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)