Raven 4.0 Replication

[Anders Strömberg]

Hi,

I can't find much documentation about replication in 4.0,  maybe someone here has some insight.

We currently have one server in Sweden and one in China. Most databases are setup as master to master replication since we want all our production data created in China to be easily available in Sweden and vice versa. In order to avoid collisions in document naming we use the Raven/ServerPreFixForHiLo document, will this still work?

Also we are currently doing "Bad Things"™ and not replicating some settings documents by applying   "Raven-Not-For-Replication": "True" in their meta-data, is the recommendation to move these out to a separate database instead?

BR
Anders

[Oren Eini (Ayende Rahien)]

In 4.0, there is no need for ServerPreFixForHiLo, that is the node tag that is already included by default.

There is no such option for skipping replication of some documents in 4.0, you'll need to either use ETL process between the nodes (they won't be the same db group) and you can filter data or you can use separate databases.

I got into a lot of details around that in the book: https://github.com/ravendb/book/releases

Chapter 6, 7 and 8 talk about the distributed model extensively, and I would love feedback.

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Anders Strömberg]

Thanks, will read the chapters ASAP.

BR
Anders

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.