Maxim Khutornenko created AURORA-1500:
-----------------------------------------
Summary: Platform SLA gets stuck in DOWN when a replacement
PENDING is killed
Key: AURORA-1500
URL: https://issues.apache.org/jira/browse/AURORA-1500
Project: Aurora
Issue Type: Bug
Components: Scheduler
Reporter: Maxim Khutornenko
The way platform SLA calculation is currently done cannot account for some
special cases when killed tasks don't leave any history behind. One example: a
task gets LOST (SLA DOWN interval starts) and its replacement is scheduled
immediately. If, however, the replacement task gets killed while still in
PENDING, no history is left to close the DOWN interval and the platform SLA is
degraded until either a new matching instance task is created by user or the
task history is purged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
