aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <>
Subject [jira] [Commented] (AURORA-1240) Deprecate UpdateConfig "restart_threshold" setting
Date Mon, 06 Apr 2015 23:21:13 GMT


Bill Farner commented on AURORA-1240:

Opting to make no client change for now, so that the 0.8.0 client is compatible with the 0.7.0

> Deprecate UpdateConfig "restart_threshold" setting
> --------------------------------------------------
>                 Key: AURORA-1240
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Bill Farner
> The UpdateConfig {{restart_theshold}} \[1\] setting does not appear to deliver much user
value as it's highly sensitive to scheduling performance and may result in aborted/rolled
back job updates when set too low.
> Some background: This timeout controls task transition from {{PENDING}} to {{RUNNING}}
during the job update. In the event of cluster capacity shortage, assigning a task to a host
may take considerably longer thus expiring the timeout and depending on the failure settings
causing an unnecessary job update abort or rollback. It was meant to give users some protection
against unsatisfiable resource/constraint requirements. In reality though, it proved to be
rather an annoyance to users when an update is interrupted due to unexpected delay in task
> Consider deprecating and subsequently removing this setting.
> \[1\] -

This message was sent by Atlassian JIRA

View raw message