aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1242) Consider new task states to track package fetching and task launching
Date Sun, 20 Dec 2015 15:20:46 GMT

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

Stephan Erb commented on AURORA-1242:
-------------------------------------

This seems partially addressed by https://issues.apache.org/jira/browse/AURORA-1225. 

> Consider new task states to track package fetching and task launching
> ---------------------------------------------------------------------
>
>                 Key: AURORA-1242
>                 URL: https://issues.apache.org/jira/browse/AURORA-1242
>             Project: Aurora
>          Issue Type: Story
>          Components: Executor, Scheduler
>            Reporter: Maxim Khutornenko
>
> There is currently little to no visibility into task launching activities. Once a task
reaches {{RUNNING}} it's considered entering an application realm where the only way to dissect
the warmup period is through examining thermos processes (if they exist). The warmup may take
arbitrary long time to complete exacerbating the visibility problem even further. 
> Another example is docker container pull (AURORA-1059) where a task stays in {{ASSIGNED}}
until a docker pull completes. This skews our SLA metrics and risks aborting the task due
to exceeding transient task timeout.
> We should consider adding more task states to track package/container fetch and launching/warmup
activities explicitly, e.g.:
> {{ASSIGNED}} -> {{FETCHING}} ->{{LAUNCHING|STARTING}} -> {{RUNNING}}
> The above would require modifying the schema to require explicit definition for package
fetching.



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

Mime
View raw message