1 |
Hi |
2 |
|
3 |
Very interesting links, read through them quickly. |
4 |
Most seem to offer replication-alike setups with various twists. |
5 |
|
6 |
I'm unsure if there is an official definition of a clustered |
7 |
database, but I meant one in the sense that it's used for Oracle |
8 |
cluster & Mysql cluster. IOW fragments of your data reside in |
9 |
multiple copies on the database-datanodes. You end up talking to the |
10 |
SQL frontend which uses some way of finding the correct fragment of |
11 |
data on your data-nodes. |
12 |
|
13 |
I think (but am not sure) that to call a database solution a cluster |
14 |
it would need to be able to store a larger total datavolume than the |
15 |
storage-space of a single node. |
16 |
|
17 |
If it doesn't do that, it's a replication setup. |
18 |
|
19 |
Don't get me wrong, replication is extremely useful and we're making |
20 |
heavy use of it. |
21 |
However, as far as I've always understood multi-master aka multi- |
22 |
write replication is very error-prone and unstable. Which seems |
23 |
logical to me if I try to imagine what should happen in a replication- |
24 |
setup when two clients are trying to update the same table with an |
25 |
autoincrement field at the same time on different replicationhosts. |
26 |
|
27 |
I'd be interested in anyone's experiences with multi-master |
28 |
replication setups, anyone running one ? |
29 |
|
30 |
Thanx for the links ;-) |
31 |
|
32 |
Ramon |
33 |
-- |
34 |
In the beginning, there was nothing. And God said, 'Let there be Light.' |
35 |
And there was still nothing, but you could see a bit better. |
36 |
|
37 |
|
38 |
|
39 |
-- |
40 |
gentoo-cluster@g.o mailing list |