aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <>
Subject [jira] [Commented] (AURORA-490) aurora create fail due to incorrect UpdateConfig.watch_secs
Date Thu, 29 May 2014 23:08:01 GMT


Bill Farner commented on AURORA-490:

It break the current behavior. I think it should be documented, perhaps in release notes?

Unfortunately we don't have release notes right now as we've yet to complete our first release.
 We have started exercising a more formalized deprecation process (evidence of tracking here:
AURORA-423).  However, it would have been good form for us to notify on the mailing list.
 In this particular case, we realized after the fact that a change in client updater behavior
(removing client-side health checks during updates: AURORA-361) created a case where updates
could be extremely risky if these two parameters were misaligned.  We decided it was better
to prevent an update like this to mitigate risk.

> aurora create fail due to incorrect UpdateConfig.watch_secs
> -----------------------------------------------------------
>                 Key: AURORA-490
>                 URL:
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.6.0
>            Reporter: Bhuvan Arumugam
> The create fail, if {{HealthCheckConfig.initial_interval_secs}} is specified and {{UpdateConfig.watch_secs}}
is not specified.
> If {{UpdateConfig.watch_secs}} is not specified, it should default to sensible default.
It should report following error only if the user have defined {{UpdateConfig.watch_secs}}
and it is lesser than expected seconds.
> {code}
> [bhuvan@scheduler apps]$ aurora create int/bhuvan/staging10/AppName AppName.aurora 
> You have specified an insufficiently short watch period (45 seconds) in your update configuration.
> Your update will always succeed. In order for the updater to detect health check failures,
> UpdateConfig.watch_secs must be greater than 330 seconds to account for an initial
> health check interval (180 seconds) plus 5 consecutive failures at a check interval of
30 seconds.
> {code}

This message was sent by Atlassian JIRA

View raw message