aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-894) Server updater should watch healthy instances
Date Mon, 13 Apr 2015 16:36:12 GMT

     [ https://issues.apache.org/jira/browse/AURORA-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Khutornenko updated AURORA-894:
-------------------------------------
    Description: 
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}} - https://github.com/apache/incubator-aurora/blob/master/docs/configuration-reference.md#healthcheckconfig-objects
  {{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. 

  was:
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}} - https://github.com/apache/incubator-aurora/blob/master/docs/configuration-reference.md#healthcheckconfig-objects
  {{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 feature requires AURORA-279.


> Server updater should watch healthy instances
> ---------------------------------------------
>
>                 Key: AURORA-894
>                 URL: https://issues.apache.org/jira/browse/AURORA-894
>             Project: Aurora
>          Issue Type: Epic
>          Components: Scheduler
>            Reporter: 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}} - https://github.com/apache/incubator-aurora/blob/master/docs/configuration-reference.md#healthcheckconfig-objects
>   {{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
(v6.3.4#6332)

Mime
View raw message