Uploaded image for project: 'Aurora'
  1. Aurora
  2. AURORA-324

Migrate from Twitter ShutdownRegistry to Guava ServiceManager

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.0
    • Reliability, Scheduler
    • None

    Description

      Right now the scheduler uses the (synchronous, sequential) ShutdownRegistry which can lead to deadlocks at shutdown. Migrate to (asynchronous, parallel) ServiceManager [1,2] and add an endpoint to inspect the state of individual services running within the scheduler.

      [1] https://code.google.com/p/guava-libraries/wiki/ServiceExplained
      [2] http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/util/concurrent/ServiceManager.html

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. AURORA-327 Aurora shutdown blocks when attempting to abdicate leadership and zk ensemble is down

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. AURORA-325 Scheduler shutdown commands should execute asynchronously

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              kevints Kevin Sweeney
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: