hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@yahoo-inc.com>
Subject Re: Design Q: logging/nesting of exceptions
Date Fri, 09 May 2008 16:56:11 GMT

On May 9, 2008, at 2:03 AM, Steve Loughran wrote:
> Owen O'Malley wrote:
>> On May 8, 2008, at 10:21 AM, Doug Cutting wrote:
>>> I'd go with something closer to an accidental policy.  My  
>>> suspicion is that logging framework didn't print nested  
>>> exceptions well.  Owen is the father of stringifyException and  
>>> may have more insight.
>> Yeah, it was my fault. The log4j was misconfigured, so we didn't  
>> get the exception traces out of the messages. I didn't realize it  
>> was a misconfiguration until much later and it had become standard  
>> practice within Hadoop. *sigh* I've fixed a couple of them, but  
>> there are a lot more.
> OK, that means when I encounter them I can change them.
> Somewhere on my todo list is way better Junit reports, including  
> logs from multiple machines and stack traces in machine readable  
> form...getting the exceptions out raw is one of the requirements  
> for this to work
> http://wiki.apache.org/ant/Proposals/EnhancedTestReports
> -steve

Hey Steve,

Hope Hudson is on your list of CI servers to test wrt to Ant Junit  
report changes :-)

On another note, have you used SmartFrog to config/deploy Hadoop?  If  
so, I'm interested in your experiences.

Y! Grid QE Manager

View raw message