1. you can use a mysql slave for snapshot only. This instance will be used
for backup only and not for your reads. This is not the most cost effective
solution, but this avoid a delay after a snapshot.2. if you start a new
slave, restart mysql-proxy only when the new slave is in sync with the
master.

On Wed, Sep 16, 2009 at 2:42 AM, favo <[email protected]> wrote:

>
> Thanks for your feedback Frederic.
>
> > Pay attention with the version of mysql-proxy you are using.
> > The problem you mentionned is not a scalr problem. This is a application
> > logic problem.
>
> > I suggest you to visit mysql forum and usual web application forum for
> this
> > purpose.
>
> I know that this is no scalr problem and only a configuration/software
> setup issue.
> But I thought the readers here will understand me easier because as
> scalr users they will have come across similar problems when using the
> mysql master/slave setups :-)
>
>
> > I suggest you should check why your slave are far behind the
> > master. You should maybe opt for a bigger instance that is known to be
> > faster.
>
> The source of my problems is that I have too many writes between the
> volume snapshots.
> Even if I do hourly snapshots the data will be one hour old and the
> new mysql slave will need some minutes to catch up the missing hour.
> In this time it will already get requests forwarded by mysql-proxy
> because it does not seem to validate how far behind a slave might be.
>
> One solution is to have mysql slaves running all the time and never
> scale based on the server load.
> Another solution is to do the load distribution in my apps and include
> the checks there, but I dont want to change them.
> A third solution might be another setup (i.e. other mysql load
> balancer), different lua scripts for mysql-proxy, some scalr scripts
> to call when the slave is in sync, etc.
>
> I was hoping to learn from the experience of other scalr users before
> going somewhere else.
>
> --
>  Mario
>
> >
>

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