aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1844) Force a snapshot at the end of Scheduler startup.
Date Fri, 02 Dec 2016 23:57:58 GMT

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

Zameer Manji commented on AURORA-1844:
--------------------------------------

This might be a dupe of AURORA-1812

> Force a snapshot at the end of Scheduler startup.
> -------------------------------------------------
>
>                 Key: AURORA-1844
>                 URL: https://issues.apache.org/jira/browse/AURORA-1844
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Santhosh Kumar Shanmugham
>            Priority: Minor
>
> When the scheduler starts up, it replays the logs from the replicated log to catch up
with the current state, before announcing itself as the leader to the outside world. If for
any reason after this replay, the scheduler dies after adding more log entires, the next startup
will have to redo the work again. This becomes problem when the amount of additional work
added is not trivial, and can take the scheduler down the path of a spiraling death. One example,
of this is when the TaskHistoryPruner cleans up the DB but adds to the log entires. In order
to avoid the repeated work, the scheduler should force a snapshot after the initial replay.



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

Mime
View raw message