[
https://issues.apache.org/jira/browse/AURORA-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013066#comment-14013066
]
Bhuvan Arumugam commented on AURORA-490:
----------------------------------------
Thank you, [~maximk]. Got it.
It break the current behavior. I think it should be documented, perhaps in
release notes?
Users upgrading aurora from previous releases should fix their aurora config to
define UpdateConfig.
> aurora create fail due to incorrect UpdateConfig.watch_secs
> -----------------------------------------------------------
>
> Key: AURORA-490
> URL: https://issues.apache.org/jira/browse/AURORA-490
> 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
> FATAL]
> 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
(v6.2#6252)
