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-1648) Use of `dbScript` field and schema changes can cause crashes
Date Tue, 22 Mar 2016 20:40:25 GMT

    [ 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)

Mime
View raw message