[OOZIE-3357] [core] More graceful CallableQueueService#destroy()

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.1.0
• Fix Version/s: 5.3.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Andras Piros
• Created: 03/Oct/18 10:10
• Updated: 20/Sep/19 09:34

Description

In OOZIE-3160 CallableQueueService has been refactored. It seems like not all the XCallable elements are processed when one of the ExecutorService instances are shut down.

Following issues to investigate:

1. ThreadPoolExecutor#awaitTermination() gets stuck even if no XCallable elements are present anymore
2. await termination only conditionally, that is, when there are still some XCallable elements in one of the ThreadPoolExecutor instances

Issue Links

• is related to: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting