Would you consider a service like www.xeround.com?
Sent from my iPad
On Jul 17, 2012, at 7:23 PM, Carl Kabbe wrote:
> On Monday, I asked if there were consultants out there who could help set up
> an NDB high availability system. As I compared our needs to NDB, it became
> obvious that NDB w
Hey all,
Apologies for this mostly-off-topic mail, but I would like to draw interested
parties' attention to the yearly Linux Bier Wanderung - the Linux Beer Hike -
that I'm helping organise this year in Diksmuide, Belgium :-)
In brief, it's more of a holiday than it is a convention, with fri
On 7/17/2012 8:22 PM, Carl Kabbe wrote:
On Monday, I asked if there were consultants out there who could help set up an
NDB high availability system. As I compared our needs to NDB, it became
obvious that NDB was not the answer and more obvious that simply adding high
availability processes t
At 06:34 AM 7/18/2012, Johan De Meersman wrote:
Hey all,
Apologies for this mostly-off-topic mail, but I would like to draw
interested parties' attention to the yearly Linux Bier Wanderung -
the Linux Beer Hike - that I'm helping organise this year in
Diksmuide, Belgium :-)
In brief, it's m
We are actually facing both capacity and availability issues at the same time.
Our current primary server is a Dell T410 (single processor, 32 GB memory) with
a Dell T310 (single processor, 16GB memory) as backup. Normally, the backup
server is running as a slave to the primary server and we ma
On 18/07/12 18:11, Carl Kabbe wrote:
> We are actually facing both capacity and availability issues at the
> same time.
>
> Our current primary server is a Dell T410 (single processor, 32 GB
> memory) with a Dell T310 (single processor, 16GB memory) as backup.
> Normally, the backup server is runn
Hello Carl,
On 7/18/2012 11:11 AM, Carl Kabbe wrote:
We are actually facing both capacity and availability issues at the same time.
...
It sounds to me like you need a combination of sharding (one master per
client or set of clients) combined with multiple slaves (one for backups
only). If y
Hello,
As far i can understand by your post, you need a high availability mysql
cluster with large capacity.
For having high availability you need something that can give you
multi-master replication between two or more mysql servers.
In my knowledge there are three solutions that can give yo
Keep in mind that all "cluster" solutions are vulnerable to a single power
failure, earthquake, flood, tornado, etc.
To "protect" from such, you need a hot backup located remotely from the "live"
setup. This introduces latency that will kill performance -- all cluster
solutions depend on synci
You could write to an InnoDB frontend with master/master replication at
each site, and slave off the local InnoDB server to your local cluster
at each site.
Would make your writes limited by your InnoDB server performance and
remote replication speed, but reads would run at cluster speeds and
10 matches
Mail list logo
