Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 04EE4200BB7 for ; Wed, 9 Nov 2016 23:48:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 03875160AFD; Wed, 9 Nov 2016 22:48:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 76C2D160AFA for ; Wed, 9 Nov 2016 23:47:59 +0100 (CET) Received: (qmail 79507 invoked by uid 500); 9 Nov 2016 22:47:58 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 79489 invoked by uid 99); 9 Nov 2016 22:47:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2016 22:47:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6C6BB2C2A69 for ; Wed, 9 Nov 2016 22:47:58 +0000 (UTC) Date: Wed, 9 Nov 2016 22:47:58 +0000 (UTC) From: "Stephan Erb (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AURORA-1812) Upgrading scheduler multiple times in succession can lead to incompatible snapshot restore MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 09 Nov 2016 22:48:00 -0000 [ https://issues.apache.org/jira/browse/AURORA-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652282#comment-15652282 ] Stephan Erb commented on AURORA-1812: ------------------------------------- +1. I had the same idea in mind. > Upgrading scheduler multiple times in succession can lead to incompatible snapshot restore > ------------------------------------------------------------------------------------------- > > Key: AURORA-1812 > URL: https://issues.apache.org/jira/browse/AURORA-1812 > Project: Aurora > Issue Type: Bug > Components: Scheduler > Affects Versions: 0.14.0 > Environment: Mesos-0.27.2 aurora-scheduler-0.14.0 > Reporter: Patrick Veasey > Priority: Minor > > When upgrading scheduler multiple times in a row there can be a situation where the snapshot is restored is from an incompatible version. Which will cause scheduler to fail to start, with SQL exceptions. Workaround is to ensure the most current snapshot was taken by the current version of aurora, either by manually starting snapshot or setting dlog_snapshot_interval to a low timeframe. > Log of failure can be found here: > https://gist.github.com/Pveasey/4ca1ad4d3ded21cd6e1674f20a8a4af3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)