Question regarding SQL Replication when add new script/mapping (2.5)

[James Tan]

Currently, on the live environment, when we add a new mapping or script, the SQL replication will only process the new added script and it could take hours to catch up and it caused other existing replication delays for hours.

Is this by design? It is annoy on the live environment with fair size DB (say 20M doc).

I thought the process should be multi-threaded.

Thanks

James

[Oren Eini (Ayende Rahien)]

It is multi threaded, but only when all replications are on the same etag.

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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Tan]

Shall this consider a problem for live environment, esp with large number of document to scan?

Thanks

James

You received this message because you are subscribed to a topic in the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ravendb/_CY-Ekhwd60/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

It might be. 

We'll be looking into improving this for 3.5