We're working on it, however It's not a separate role this time, the
existing mysqllvm role is involved and EBS is not actually used for actual
data storage, except master.
We spent quite some time  in attempt to find the best balance between
cost-effectiveness for clients, durability and speed. Any thoughts/votes are
welcome in this thread.


In short how it works:
- EBS is attached to master only.
- When slave is up, Scar creates a new volume from a master's volume
snapshot and attaches it to slave. Slave then copies data from it on it's
ephemeral device and plugs into replication.
- If master crashes - no worries, Scalr attaches the volume to a slave,
switches datadir to the volume and it becomes master.

Will create a diagram later today.

The main problems that it's supposed to solve:
1. no more "bundles + uploads/downloads to S3".
2. More data safety - more frequent snapshots of data (via EBS snaps) and
master's volume is always there, with the latest data, even if master
crashes.
- The unlimited storage size for mysql datadir feature left aside for now,
we're limited to 1.6 TB of ephemeral device on large instance.

Another minus is that with this scheme, you wont be able to have mysql
instances in different locations, because ebs volumes  are stuck to a single
location.

Also planning to create a roadmap page for features that are currently in
development.

On 16.12.08 23:28, "Kevin Baker" <[email protected]> wrote:

> I've seen some mention of a new Scalr MySQL AMI that utilizes EBS for
> storage... and handles master promotion on failover.
> 
> Is this still on the road map, and if so when should we expect release?
> 
> We are starting to build out our production Farm and want to integrate the
> EBS mysql instances if possible.
> 
> Thanks,
> 
> -- kevin
> 
> > 





--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to