[ACCUMULO-607] BatchScanner sometimes logs error when closed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 1.3.5-incubating, 1.4.0
• Component/s: client
• Assignee: Unassigned
• Reporter: Keith Turner
• Created: 25/May/12 16:52
• Updated: 28/Oct/20 23:11
• Resolved: 28/Oct/20 23:11

Description

The batch scanner has a threadpool. When the batch scanner is closed it calls shutdownNow() on this threadpool, which interrupts all of the threads. If a user does not read all data from a batch scanner and calls close, thens its likely that the background threads are still busy and will be interrupted. This is a normal course of business, so there is no need to log an exception for these interrupted excpetions. Some places in the code do log an error when these exceptions occur.

One place is where the background code calls UtilWaitThread.sleep(). There may be other places.