Hi Alexandre,
On 28/01/2010, at 11:39 AM, Alexandre Almeida wrote:
The idea behind the server_id column is to avoid inc_inc = 10, for
example. Inc_Inc/Offset is excellent for 1, 2, or even 3 MM servers.
Where things go wild, I mean, more then 3 servers, connected via
ADSL we must be more c
Hi Brian,
On 1/27/10 12:51 PM PST, "Brian Evans" wrote:
> I was reading over the replication discussion on maria-developers
> I thought I'd share some thoughts that are not so technical as I do not
> understand the back end that well.
>
> Our system is currently a master-master WAN replication
Hi Arjen,
The idea behind the server_id column is to avoid inc_inc = 10, for
example. Inc_Inc/Offset is excellent for 1, 2, or even 3 MM servers.
Where things go wild, I mean, more then 3 servers, connected via ADSL
we must be more creative.
And if you are using MyIsam you can make serv
Hi Alexandre, Brian
On 28/01/2010, at 7:18 AM, Alexandre Almeida wrote:
Allow me to share how we are handling this issue. We have a customer
that develop and sell a system that control employees in & out.
They have many customers with multiple plants & sites.
To avoid the related issue, we did
Brian,
Allow me to share how we are handling this issue. We have a customer
that develop and sell a system that control employees in & out. They
have many customers with multiple plants & sites.
To avoid the related issue, we did a simple workaround, we add a new
column at each table. T
I was reading over the replication discussion on maria-developers
I thought I'd share some thoughts that are not so technical as I do not
understand the back end that well.
Our system is currently a master-master WAN replication setup, each
writing to a different DB with an offline process to do c
6 matches
Mail list logo
