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-1015) Paused update survives past job lifetime
Date Wed, 14 Jan 2015 22:51:35 GMT

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

Maxim Khutornenko commented on AURORA-1015:
-------------------------------------------

The current job update retention period is set at 30 days. However, a paused update is still
considered active and is not a subject to pruning. So, technically the feature worked as designed.

The fact that job update remained even though its job had gone is the unfortunate reality
of Aurora not treating jobs (job keys) as first level. This will likely to change with migrating
TaskStore to H2. 

How did this issue surface itself? Did you get any abnormal error when interacting with the
job via client?

> Paused update survives past job lifetime
> ----------------------------------------
>
>                 Key: AURORA-1015
>                 URL: https://issues.apache.org/jira/browse/AURORA-1015
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Chris Lambert
>            Assignee: Maxim Khutornenko
>              Labels: twitter
>
> I left an asynchronous update paused for a month.  During that time, all the tasks in
that job died, but the paused update remained.  



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

Mime
View raw message