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-1605) Update recovery docs to reflect changes
Date Tue, 02 Feb 2016 18:54:40 GMT

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

Stephan Erb commented on AURORA-1605:
-------------------------------------

Another thing that confused us when we once tried to apply a backup was the section "Identify
the leading scheduler by" (https://github.com/apache/aurora/blob/f630bf705ac8a9de2b7b987858ada3b876f65abf/docs/storage-config.md#restore-from-backup)

* Do I have to do all of those steps, or just one one them?
* Isn't the first one supposed to always work? Meaning, if we don't have a leading scheduler,
we can't apply the remaining steps anyway?

> Update recovery docs to reflect changes
> ---------------------------------------
>
>                 Key: AURORA-1605
>                 URL: https://issues.apache.org/jira/browse/AURORA-1605
>             Project: Aurora
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Joshua Cohen
>            Priority: Minor
>
> We had to restore one of our clusters from backup recently, and it turns out there's
been some drift between the [documented process](https://github.com/apache/aurora/blob/f630bf705ac8a9de2b7b987858ada3b876f65abf/docs/storage-config.md#recovering-from-a-scheduler-backup)
and what's currently necessary.
> Specifically, we needed to disable the leader redirect filter and, I believe, mesos authentication.
> We should make sure the recovery docs are up to date with what's actually required.



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

Mime
View raw message