Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 813FD173E6 for ; Sat, 25 Oct 2014 05:15:06 +0000 (UTC) Received: (qmail 75207 invoked by uid 500); 25 Oct 2014 05:15:05 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 75120 invoked by uid 500); 25 Oct 2014 05:15:05 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 75107 invoked by uid 99); 25 Oct 2014 05:15:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Oct 2014 05:15:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of busbey@cloudera.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Oct 2014 05:14:59 +0000 Received: by mail-qc0-f182.google.com with SMTP id m20so1708064qcx.41 for ; Fri, 24 Oct 2014 22:14:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=bdm+FxyjMt3fXyr9PZHitA2Kqw6h6/YDadkDkUc6nJY=; b=U2u73EI2de1YaCCTo8VLVeJQ8Wlw6KAPGpBZudiHWTjstSXMPevv0/CQcujzdy88nc zOGURGr/dAOEJrwGvTo3toSxN7o/ONPBCqLijgQLJN/qqYYW3rhZTmeh9+fwIQYOabtZ eCjSioyvxEYxirl8Fc3VGMLa5ziCCcqcHX9t3amngKuh5Snwh5NNLzs11d11QqWvTBca yhdM3Bv6rvEAg1LkZCIhTI3XypF7SRnGfARcdCWrb+sBiv3DNpM6O12+8kFd6V8AecEL 0t6ythWMU4eDIIk7jWotPVcjA9t5Ngy5ZN4CdhpAxVoFKYJSrofm8xTUm4+8R6ptUguy FNew== X-Gm-Message-State: ALoCoQmkSbqKqmg958qxPcd6Tceu0xMfXiupRyV/xJjgsrR6PypUXjovpZPBq1WZyNVKd95KMjg+ X-Received: by 10.224.152.5 with SMTP id e5mr12218106qaw.48.1414214079204; Fri, 24 Oct 2014 22:14:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.104.136 with HTTP; Fri, 24 Oct 2014 22:14:18 -0700 (PDT) From: Sean Busbey Date: Sat, 25 Oct 2014 00:14:18 -0500 Message-ID: Subject: Reworking the use of log levels To: dev Content-Type: multipart/alternative; boundary=047d7b2eda3bd3e3a90506385fdb X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2eda3bd3e3a90506385fdb Content-Type: text/plain; charset=UTF-8 Hi! Right now we have many failure paths where we send stack traces to log files at ERROR / WARN. In an effort to make things easier to operate, I'd like to propose we move towards: * INFO/WARN/ERROR : description of failure and if possible an action an operator could take to fix/diagnose * DEBUG : information needed to handle failures that require developer action, i.e. stack traces I figure this can go as one or more subtasks off of HBASE-12341, but wanted to float things here before I get started. -- Sean --047d7b2eda3bd3e3a90506385fdb--