> The approach that should be taken is:
>
> 1) Set up master -> slave replication
> 2) Change policyd so that all READS happen from the slave(s)
>and WRITES only go to the master.
I personnaly like this since I have already replicated system like
that with severals slaves... and a loadbalancer
Stanislav Sinyagin wrote:
> --- Cami Sardinha <[EMAIL PROTECTED]> wrote:
>> And what happens when someone requests a 3rd, 4th and 5th MySQL
>> backup option?
>
> nobody would need that :)
> The approach that I suggested would work perfectly for 1+1 redundancy.
> If someone wants a bigger redundan
--- Cami Sardinha <[EMAIL PROTECTED]> wrote:
> And what happens when someone requests a 3rd, 4th and 5th MySQL
> backup option?
nobody would need that :)
The approach that I suggested would work perfectly for 1+1 redundancy.
If someone wants a bigger redundancy solution, it would anyway require
> --- Stanislav Sinyagin <[EMAIL PROTECTED]> wrote:
>
>> It would be great to implement a new option in policyd.
>> Technically it should not be difficult.
>>
>> The new option would list a backup MySQL server/dbname/user/password,
>> and if it's specified, every INSERT statement is duplicated on
On Mon, Aug 06, 2007 at 12:13:50PM +0200, Cami Sardinha wrote:
> And what happens when someone requests a 3rd, 4th and 5th MySQL backup
> option?
I agree that duplication INSERT and UPDATE requests to multiple databases
is not policyd's job, this should be implemented in a MySQL replication
system
Stanislav Sinyagin wrote:
> It would be great to implement a new option in policyd.
> Technically it should not be difficult.
>
> The new option would list a backup MySQL server/dbname/user/password,
> and if it's specified, every INSERT statement is duplicated on that server.
>
> This would al
every INSERT and UPDATE, of course :)
--- Stanislav Sinyagin <[EMAIL PROTECTED]> wrote:
> It would be great to implement a new option in policyd.
> Technically it should not be difficult.
>
> The new option would list a backup MySQL server/dbname/user/password,
> and if it's specified, every I
It would be great to implement a new option in policyd.
Technically it should not be difficult.
The new option would list a backup MySQL server/dbname/user/password,
and if it's specified, every INSERT statement is duplicated on that server.
This would allow an elegant redundant solution: two p
