hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@cloudera.com>
Subject Re: Reworking the use of log levels
Date Sat, 25 Oct 2014 13:34:09 GMT
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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message