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] [Commented] (AURORA-1631) Consider removing --restart-threshold from "aurora job restart"
Date Fri, 22 Apr 2016 21:55:12 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254763#comment-15254763
] 

Maxim Khutornenko commented on AURORA-1631:
-------------------------------------------

https://reviews.apache.org/r/46587

> Consider removing --restart-threshold from "aurora job restart"
> ---------------------------------------------------------------
>
>                 Key: AURORA-1631
>                 URL: https://issues.apache.org/jira/browse/AURORA-1631
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Maxim Khutornenko
>
> We have removed {{restart_threshold}} from the updater (AURORA-479, AURORA-1252, AURORA-1254)
but it's still a valid option of the "aurora job restart". It's now causing similar end user
issues (interrupted restarts due to low default value of 60 seconds) and results in inconsistent
user expectations. 
> Consider removing this option as it does not deliver much value and uses the old and
now defunct {{restart_threshold + watch_secs}} formula for watching instance health. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message