If your slave has the latest data, simply terminate the master and the slave will be promoted to master, and a new instance launched as a slave. Does that help?
On Fri, Jan 14, 2011 at 10:47 PM, greenham <[email protected]> wrote: > As you probably know, Amazon was having some big EBS issues this > morning in US-EAST. My mysql master EBS volume is now gone. There is > a snapshot, so I should be fine, but when a new master tries to start > it just keep spewing "Error: no such volume: 'vol-6b34cb02' > > When I look in master-snap.conf, there is nothing referencing that > volume, but rather EBS_SNAP_ID of snap-05214e68 (which was the last > snapshot of vol-6b34cb02 > > I still have one slave running that has the latest data as well. > > Any advice on how we can resolve this? > > -- > 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]<scalr-discuss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/scalr-discuss?hl=en. > > -- 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.
