JobTracker.close() prints stack traces for exceptions that are not errors
-------------------------------------------------------------------------
Key: HADOOP-2323
URL: https://issues.apache.org/jira/browse/HADOOP-2323
Project: Hadoop
Issue Type: Bug
Components: mapred
Affects Versions: 0.16.0
Reporter: Jim Kellerman
Assignee: Jim Kellerman
Fix For: 0.16.0
JobTracker.close() prints a stack trace for an interrupted exception even
though it was the method that interrupted the thread that threw the exception.
For example:
{code}
this.expireTrackers.stopTracker();
try {
this.expireTrackersThread.interrupt();
this.expireTrackersThread.join();
} catch (InterruptedException ex) {
ex.printStackTrace();
}
{code}
Well of course it is going to catch an InterruptedException after it just
interrupted the thread!
This is *not* an error and should *not* be dumped to the logs!
In other circumstances, catching InterruptedException is entirely appropriate.
Just not in close where you've told the thread to shutdown and then interrupted
it to ensure it does!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
