Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3357

[core] More graceful CallableQueueService#destroy()

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 5.1.0
    • 5.3.0
    • core
    • None

    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

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              andras.piros Andras Piros
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: