On Wed, Mar 11, 2009 at 12:41 PM, Alex Kovalyov <[email protected]>wrote:
> > > > > On 11.03.09 21:20, "Frédéric Sidler" <[email protected]> wrote: > > > mysql EBS : persistency of your data in any case and particulary in case > of > > an instance crash. No more need to backup an instance every hour ;-)32 vs > 64 > > : CPU speed, RAM, network access > > > > On Wed, Mar 11, 2009 at 4:19 PM, Kevin Baker <[email protected]> > wrote: > > > >> > >> Can someone give an overview of the advantages in using mysql EBS? > > Community members were demanding it, we responded. I guess most of users > associate EBS with with data safety and blindly wish to use it. Ok, well I think if I had only a single database server this would be the case. I'm not sure if that is the case for a master/slave setup that has proper snapshots/backups. What would be the behavior of the master-ebs/slave setup if the master-ebs went down? Is the slave also EBS? If not what happens to the orphaned EBS instance that was attached to the master? Just curious how this master/slave promotion workflow works with EBS. > > >> > >> Also what would be the performance advantages to using 64 vs 32? > >> I think I saw performance > >> > >> > >> On Mar 11, 2009, at 4:13 AM, "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 -~----------~----~----~----~------~----~------~--~---
