Qiang has made a point. +1 On Oct 25, 2014, at 5:10 AM, Qiang Tian <tian...@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 <bus...@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 >>
