[jira] [Resolved] (AURORA-324) Migrate from Twitter ShutdownRegistry to Guava ServiceManager

["Bill Farner (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AURORA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Farner resolved AURORA-324.
--------------------------------
    Resolution: Fixed

I believe this was addressed with:
{noformat}
commit b6217df13b5615e4c76835a3ed94e3e9a89a22a2
Author: Kevin Sweeney <ke...@apache.org>
Date:   Fri Nov 21 10:35:11 2014 -0800

    Replace bindStartupAction with Service registration
    
    This attempts to kill LifecycleModule in favor of service registration.
    
    Testing Done:
    ./gradlew -Pq build
    
    Bugs closed: AURORA-920
    
    Reviewed at https://reviews.apache.org/r/27757/
{noformat}

> Migrate from Twitter ShutdownRegistry to Guava ServiceManager
> -------------------------------------------------------------
>
>                 Key: AURORA-324
>                 URL: https://issues.apache.org/jira/browse/AURORA-324
>             Project: Aurora
>          Issue Type: Task
>          Components: Reliability, Scheduler
>            Reporter: Kevin Sweeney
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)