You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2015/03/02 18:57:04 UTC
[jira] [Updated] (AURORA-1097) Scheduler updater should suppress
instance events on resume
[ https://issues.apache.org/jira/browse/AURORA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Khutornenko updated AURORA-1097:
--------------------------------------
Sprint: Twitter Aurora Q1'15 Sprint 4
> Scheduler updater should suppress instance events on resume
> -----------------------------------------------------------
>
> Key: AURORA-1097
> URL: https://issues.apache.org/jira/browse/AURORA-1097
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
> Priority: Minor
>
> Scheduler updater does not attempt to suppress redundant instance events in case an update is paused/blocked and is subsequently resumed/pulsed. This leads to a useless sequence of no-op instance events, which may quickly consume the allocated event cap (tracked in AURORA-1096).
> For example, an update paused/resumed 2 times after instance 1 is updated will generate the following instance sequence:
> 1=[INSTANCE_UPDATING, INSTANCE_UPDATED, INSTANCE_UPDATING, INSTANCE_UPDATED, INSTANCE_UPDATING, INSTANCE_UPDATED]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)