Affects Version/s: 0.16.0
Fix Version/s: 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:
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!
|Priority||Major [ 3 ]||Minor [ 4 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Component/s||mapred [ 12310690 ]|