http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Rafal, for load-balancing reasons. If you don't need load balancing, why use master-master? I would use master-slave with failover.http://ayende.com/136198/ravendb-replication-master-master-support#comment7http://ayende.com/136198/ravendb-replication-master-master-support#comment7Wed, 23 Nov 2011 14:09:09 GMTTobi, usually you set up replication and failover because your documents are of high value to you :) why bother if they aren'thttp://ayende.com/136198/ravendb-replication-master-master-support#comment6http://ayende.com/136198/ravendb-replication-master-master-support#comment6Wed, 23 Nov 2011 12:11:24 GMTAyende, I fully agree. But there are two things that make this simple strategy a credible choice: a) The time window where conflicts can occur is very small because of replication speed (low chance of conflicts). b) Many documents are of low value individually (think of blog comments, forum posts, ...).http://ayende.com/136198/ravendb-replication-master-master-support#comment5http://ayende.com/136198/ravendb-replication-master-master-support#comment5Wed, 23 Nov 2011 10:52:00 GMTTobi, The T-1 version is an order for 1 million dollar. The T version is a modification of the user's name. Which one of them do you want to keep? How do you make that determination without actually knowing the domain? That is why we give you a way in, but don't make a decision ourselves.http://ayende.com/136198/ravendb-replication-master-master-support#comment4http://ayende.com/136198/ravendb-replication-master-master-support#comment4Wed, 23 Nov 2011 10:46:54 GMTI think a very practical and simple resolution strategy would be to choose the newest doc according to the tome on the server that generated the version. With synchronized clocks this should be a convenient default.http://ayende.com/136198/ravendb-replication-master-master-support#comment3http://ayende.com/136198/ravendb-replication-master-master-support#comment3Wed, 23 Nov 2011 10:44:10 GMTPhilip, What happen if you have multiple nodes? And you bring one online just after the original master recovered. Also, how do you (operationally speaking) know which one is the actual master?http://ayende.com/136198/ravendb-replication-master-master-support#comment2http://ayende.com/136198/ravendb-replication-master-master-support#comment2Wed, 23 Nov 2011 10:29:11 GMTWhen the primary server comes back online, can you make it the slave, so rather than switching the master back over and dealing with possible conflicts. You just make the failed master, a slave, and the fail-over stays the master. This was one of the big changes that happened to SQL Server 2008 (or was it 2005?) http://ayende.com/136198/ravendb-replication-master-master-support#comment1http://ayende.com/136198/ravendb-replication-master-master-support#comment1Wed, 23 Nov 2011 10:22:52 GMT