aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <>
Subject [jira] [Resolved] (AURORA-734) document the behavior of finalization_wait in thermos
Date Sat, 06 Feb 2016 22:30:39 GMT


Stephan Erb resolved AURORA-734.
    Resolution: Fixed

> document the behavior of finalization_wait in thermos
> -----------------------------------------------------
>                 Key: AURORA-734
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>          Components: Documentation
>            Reporter: brian wickman
>            Assignee: Stephan Erb
>            Priority: Minor
> From
> The current state of affairs is that the default finalization is 30 seconds.  Thermos
supports something called the "preemption notice" which roughly translates to "how long we'll
allow this task to finalize before we kill everything no matter what."  The idea of preemption
notice is that you may have somebody who needs the resources with a higher priority, but is
only willing to wait a fixed amount of time for its predecessor to clean up.  (More altruistic
preemptors will make this value high if they don't need the resources immediately, e.g. a
high priority batch job, but a revenue-critical task could very well make this 0 seconds and
give you no opportunity to finalize.)
> We never integrated preemption notice into Aurora because the use-case never materialized
(also, for many, preemption is fairly rare.)  Instead Thermos just uses a default of 60 seconds.
 This means that no matter how big you make the finalization wait, it can never be longer
than 60 seconds before Thermos kills everything, so keep that in mind before you use this
feature heavily.

This message was sent by Atlassian JIRA

View raw message