When running Hadoop with DEBUG logging on, this IOException was actually responsible for well-over 90% of the lines of text in my logs, making them unreadable.
We actually removed this on trunk: https://issues.apache.org/jira/browse/HADOOP-6312 - Aaron On Thu, Nov 19, 2009 at 5:29 AM, Steve Loughran <ste...@apache.org> wrote: > Rekha Joshi wrote: > >> Hi Sonal, >> >> AFAIK,this exception mostly has no impact other than to indicate object >> creation.I agree Hadoop configuration class can be improved to handle it. >> > > >> if (LOG.isDebugEnabled()) { >> LOG.debug(StringUtils.stringifyException >> (new IOException("config(config)"))); >> } >> >> I am bafflled by this block of code. Why is an IOException being thrown if >> the log level is set to DEBUG ? It would be great if someone could shed >> some >> light on this. >> >> > This is covered under > https://issues.apache.org/jira/browse/HADOOP-2851 > > It's clearly there to help debug obscure configuration constructor events. > What may be best is to move it to its own log (something related to > constructors?) so that it only comes on if you ask for an explicit log. >
