[IOTDB-3958] Add error logging for inner thread pool

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: master branch
• Component/s: Core/Engine
• Labels: pull-request-available
• Assignee: Eric Pai
• Reporter: Eric Pai
• Created: 26/Jul/22 01:50
• Updated: 27/Jul/22 02:47
• Resolved: 26/Jul/22 06:30

Description

Although we have encapsulated ThreadPools in IOTDB, unexpected exceptions in the thread will be thrown without any logging. That may cause the issue tracking very hard.

The Thread.UncaughtExceptionHandler is not worked in ThreadPoolExecutor.submit() and its subclasses, as the task in runWorker() is an instance of FutureTask, which will not throw any exception even if any error occurs in run(), and we can only get the exceptions in afterExecute. See the codes below:

In FutureTask, we can see that the exceptions are caught, not thrown directly.

Issue Links

• links to: GitHub Pull Request #6772