You are absolutely correct. The slave instance which is promoted to be master uses its current MySQL data, which is in any case more current then the last snapshot data.
Thanks On Thu, Mar 12, 2009 at 8:16 PM, Kevin Baker <[email protected]> wrote: > So, to clarify how does the current non-EBS mysql role work with master > promotion? > > I was under the impression it worked like this: > 1. slave is replicating from master > 2. it might have some replication latency depending on the application > 3. master goes down > 4. Scalr discovers it is down > 5. Scalr promotes the slave to master role, > 6. The new master uses it's current data with out grabbing new data from > backups. So it is using whatever data it had previously replicated from the > master, which is likely more current than the last backup. > 7. Scalr brings up a new slave that will replace the previous master > instance. It will be setup as a slave to the new master. > > Is this correct? If not can someone clarify? I am most interested in how the > slave gets its data when it is promoted. I am hoping it just uses what it > has from replication, since I feel like that is the most current and would > allow for much faster promotion. > > I think this information would be necessary in order to decide which mysql > role is best for our needs. > > > Thanks > > > > On Thu, Mar 12, 2009 at 8:37 AM, lorenzo.caldara <[email protected]> > wrote: >> >> Hi Igor, I miss something. I have a custom Mysql role and two >> instances based on it, one Master instance and one Slave instance. >> >> How do I move the data from the old Mysql instance to the newly >> created EBS volumes attached to the MysqlVlm instance? >> >> Thanks >> Lorenzo >> >> On Mar 11, 12:13 pm, "Igor V. Savchenko (DicsyDel)" >> <[email protected]> wrote: >> > I. Migration: >> > 1) If you use custom mysql role or non mysqllvm role you sholud: >> > a) Terminate your farm >> > b) Remove mysql role from your farm and add mysqllvm role. >> > c) On MySQL Options tab select EBS as MySQL data storage engine >> > and >> > specify size for EBS volume. >> > d) Save & launch farm. >> > >> > 2) If you already using mysqllvm role you should: >> > a) Terminate your farm >> > b) Remove mysqllvm role from farm and save it. >> > c) Edit your farm ad add mysqllvm role once again. >> > d) On MySQL Options tab select EBS as MySQL data storage engine >> > and >> > specify size for EBS volume. >> > e) Save & launch farm. >> > >> > II. Backups & Snapshoting: >> > Backups and snapshots created via EBS snapshots. >> > >> > III. mysql and mysql64 roles are deprecated. You cannot use them for >> > the new farms. >> > From now the only MySQL role is mysqllvm (mysqllvm64) and you can >> > choose the storage engine for it from either LVM, ephemeral devices or >> > EBS. >> > >> > On Mar 11, 12:48 pm, Arie Fishler <[email protected]> wrote: >> > >> > >> > >> > > Am I missing something? There are only mysqllvm roles under the shared >> > > database roles >> > >> > > On Wed, Mar 11, 2009 at 12:43 PM, Arie Fishler <[email protected]> >> > > wrote: >> > > > Great....at last EBS-MySql. Thanks. >> > >> > > > Any recommended procedure to migrate from mysqllvm to the EBS >> > > > version? >> > >> > > > What's the backup mechanism used for the MYSQL-EBS? Snapshots of the >> > > > EBS? >> > >> > > > Can you elaborate on the details/implications of this important >> > > > capability? >> > >> > > > Thanks, >> > > > Arie. >> > >> > > > On Wed, Mar 11, 2009 at 12:36 PM, Igor V. Savchenko (DicsyDel) < >> > > > [email protected]> wrote: >> > >> > > >> Intridea and Scalr team would like to announce some new features >> > > >> that >> > > >> were recently added on Scalr.net >> > >> > > >> * EBS for MySQL role (A single EBS volume is used as datadir on >> > > >> master >> > > >> and to deliver latest data to slaves (via snapshots).) >> > > >> * Elastic IPs re-assigning to a same instance within a role >> > > >> * Cloudfront support >> > > >> * New Scripting events: beforeHostTerminate, beforeInstanceLaunch >> > > >> * New variables for scripting engine: "instance_index", "region", >> > > >> "avail_zone" >> > > >> * Ability to remove image and de-register AMI during role deletion. >> > > >> * Various bugfixes and improvements. >> > >> > > >> Also, opensource version was updated to RC4. Changelog is available >> > > >> here: >> > >> > > >> > > >> >>http://groups.google.com/group/scalr-discuss/browse_thread/thread/4a2...Hide >> > > >> quoted text - >> > >> > > - Show quoted text - >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
