You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2014/04/16 21:24:15 UTC

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

Kevin Sweeney created AURORA-324:
------------------------------------

             Summary: 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.2#6252)