aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sweeney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1511) PreemptorService failure does not trigger shutdown
Date Thu, 01 Oct 2015 20:26:27 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940363#comment-14940363
] 

Kevin Sweeney commented on AURORA-1511:
---------------------------------------

It looks like we don't register a Listener on our ServiceManagers to shutdown the JVM / execute
a shutdown action as described in http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/util/concurrent/ServiceManager.html.
I think we should adopt our use of the library to more-or-less copy the pattern presented
in ServiceManager's javadoc.
I think this is a regression, as such I would block 0.10.0 until this is released.


> PreemptorService failure does not trigger shutdown
> --------------------------------------------------
>
>                 Key: AURORA-1511
>                 URL: https://issues.apache.org/jira/browse/AURORA-1511
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Zameer Manji
>
> While observing AURORA-1510 in production I noticed the bug caused the {{PreemptorService}}
to transition to the FAILED state. The {{/services}} endpoint had:
> {noformat}
> {
> name: "PreemptorService",
> state: "FAILED",
> failureCause: "java.util.ConcurrentModificationException"
> },
> {noformat}
> However the scheduler continued to run. I believe this is a bug.



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

Mime
View raw message