[
https://issues.apache.org/jira/browse/AURORA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940317#comment-14940317
]
Bill Farner commented on AURORA-1511:
-------------------------------------
I realized this lack of failure handling as well when doing scheduler lifecycle
refactoring. I think we should add a listener to our service managers that
will trigger shutdown.
> 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)
