Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of busbey@cloudera.com designates
 209.85.192.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMZUsP65w2A4JE6NaUuVc-S61-rh3F36J3TyGo5gTKkOGV=JHA@mail.gmail.com>
References: 
 <CAGHyZ6JkMukFGrLSw5wOdrg3ct180do8wN41e_w23158dezMuQ@mail.gmail.com>
	<CAMZUsP65w2A4JE6NaUuVc-S61-rh3F36J3TyGo5gTKkOGV=JHA@mail.gmail.com>
Date: Sat, 25 Oct 2014 08:34:09 -0500
Message-ID: 
 <CAGHyZ6+V4gvMbQaEKqqurVqGuLCEx-=musNqa1x+HHPg-Xqhhw@mail.gmail.com>
Subject: Re: Reworking the use of log levels
From: Sean Busbey <busbey@cloudera.com>
To: dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1133c67284ead905063f5ae3

--001a1133c67284ead905063f5ae3
Content-Type: text/plain; charset=UTF-8

Even if debug is disabled in production, it could be enabled on a
non-production system for reproducing the problem, no?

-- 
Sean
On Oct 25, 2014 7:11 AM, "Qiang Tian" <tianq01@gmail.com> wrote:

> perhaps case by case is better. stacktrace is one of most important problem
> determination methods.  debug is mostly disabled in production, we may lose
> important clues.
>
>
> On Sat, Oct 25, 2014 at 1:14 PM, Sean Busbey <busbey@cloudera.com> wrote:
>
> > 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
> >
>

--001a1133c67284ead905063f5ae3--