Master-master replication

[Suhail Doshi]

How does lightcloud handle contention issues with master-master replication, in the tokyo cabinet docs, it talks about a possible problem where the nodes can get out of sync. Does lightcloud do anything to support this? If not seems like it should be more apparent in the lightcloud docs since one of the advertised features is master-master replication but there's a clear problem that make it unsafe to use.

Suhail

[amix]

Could you link to the problem - - as I am unaware of any issues
related to master-master replication (and at Plurk we use
master-master replication in a cloud of millions of keys without any
synchronization problems).

Regards,
Amir ( http://amix.dk/ )

2009/6/19 Suhail Doshi <digital...@gmail.com>:

[Suhail Doshi]

http://tokyocabinet.sourceforge.net/tyrantdoc/

Excerpt:
"Tokyo Tyrant supports "dual master" replication which realizes higher availability. To do it, run two servers which replicate each other. Note that updating both of the masters at the same time may cause inconsistency of their databases. By default, the servers do not complain even if inconsistency is detected. The option `-rss' make them check the consistency and stop replication when inconsistency is detected."

--
http://mixpanel.com
Blog: http://blog.mixpanel.com

[amix]

LightCloud distributes both reads and writes among the masters, so the
load is balanced and each key has a master selected that it tries out
first (this way we solve replication lags and the problem of updating
a key on both masters).

Regards,
Amir

2009/6/19 Suhail Doshi <digital...@gmail.com>: