Return-Path: X-Original-To: apmail-aurora-issues-archive@minotaur.apache.org Delivered-To: apmail-aurora-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0302519F39 for ; Tue, 22 Mar 2016 20:40:26 +0000 (UTC) Received: (qmail 10244 invoked by uid 500); 22 Mar 2016 20:40:25 -0000 Delivered-To: apmail-aurora-issues-archive@aurora.apache.org Received: (qmail 10199 invoked by uid 500); 22 Mar 2016 20:40:25 -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 10190 invoked by uid 99); 22 Mar 2016 20:40:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Mar 2016 20:40:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 69C692C14DC for ; Tue, 22 Mar 2016 20:40:25 +0000 (UTC) Date: Tue, 22 Mar 2016 20:40:25 +0000 (UTC) From: "Zameer Manji (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AURORA-1648) Use of `dbScript` field and schema changes can cause crashes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AURORA-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207247#comment-15207247 ] Zameer Manji commented on AURORA-1648: -------------------------------------- Reverting the change related to step 2: https://reviews.apache.org/r/45178/ > Use of `dbScript` field and schema changes can cause crashes > ------------------------------------------------------------ > > Key: AURORA-1648 > URL: https://issues.apache.org/jira/browse/AURORA-1648 > Project: Aurora > Issue Type: Story > Reporter: Zameer Manji > > Here is a sequence of steps that can lead of a crasher: > 1. Deploy the scheduler and take a snapshot with the {{dbScript}} field populated. > 2. Upgrade the scheduler with a new version which contains schema changes (such as [~joshua.cohen]'s recent change to store Docker and AppC image ids. > 3. After upgrading, the scheduler will restore the schema of the in memory database from the {{dbScript}} field and not the built in schema. This means the table additions from the previous step will not exist. > 4. Observe crashes as queries to the in memory database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)