You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Patrick Veasey (JIRA)" <ji...@apache.org> on 2016/11/09 19:32:59 UTC

[jira] [Created] (AURORA-1812) Upgrading scheduler multiple times in succession can lead to incompatible snapshot restore

Patrick Veasey created AURORA-1812:
--------------------------------------

             Summary: 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)