[
https://issues.apache.org/jira/browse/AURORA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Erb resolved AURORA-1542.
---------------------------------
Resolution: Not A Problem
Talked to Andreas offline: We can close this as issue as life cycle methods can
be disabled so no time is spend waiting. This functionality did not exist when
the original patch has landed.
> Kill sequence delayed although HTTP teardown signal could not be dispatched
> ---------------------------------------------------------------------------
>
> Key: AURORA-1542
> URL: https://issues.apache.org/jira/browse/AURORA-1542
> Project: Aurora
> Issue Type: Bug
> Components: Executor
> Affects Versions: 0.9.0
> Reporter: Andreas Merkel
> Priority: Minor
>
> With https://issues.apache.org/jira/browse/AURORA-1275, a fix was introduced
> into Aurora 0.8.0 to avoid delaying the kill sequence in case the lifecycle
> management endpoints could not be triggered. This worked fine in version
> 0.8.0, but when upgrading to version 0.9.0, we again observed the delays
> (five seconds each after /quitquitquit and /abortabortabort were triggered),
> although our services don't implement those endpoints and return HTTP 404
> instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
