aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <>
Subject [jira] [Commented] (AURORA-894) Server updater should watch healthy instances
Date Sat, 07 Nov 2015 10:58:10 GMT


Stephan Erb commented on AURORA-894:

[~maximk] let's assume I'd like to help keep driving this epic forward. Is there a particular
order in which these tickets have to be addressed?

> Server updater should watch healthy instances
> ---------------------------------------------
>                 Key: AURORA-894
>                 URL:
>             Project: Aurora
>          Issue Type: Epic
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>              Labels: 2015-Q2
> Instead of starting the {{minWaitInInstanceRunningMs}} (aka {{watch_secs}}) countdown
when an instance reaches RUNNING state, the updater should rely on the first successful health
check instead. This will potentially speed up updates as the {{minWaitInInstanceRunningMs}}
will no longer have to be chosen based on the worst observed instance startup/warmup delay
but rather as a desired health check duration according to the following formula:
> {noformat}
> minWaitInInstanceRunningMs = interval_secs x num_desired_healthchecks x 1000
> {noformat}
> where:
>   {{interval_secs}} -
>   {{num_desired_healthchecks}} - the desired number of OK health checks to observe before
declaring an instance updated successfully
> The above would allow every instance to start watching interval depending on the individual
instance performance and potentially exit updater earlier. 

This message was sent by Atlassian JIRA

View raw message