SQL Replication and things not getting updated

[Vlad Kosarev]

This is an issue we've been having non-stop with SQL replication. Some things don't get properly replicated but there are no errors or warnings of any sort.

For example we have a document with property Status. That property goes from Valid To Paid.

We have two different replications set up for that document. Once the document moved from Valid to Paid one replication has it and the other one doesn't. This happens randomly so it's not like it's always the same replication that works and the other one doesn't.

So

document got replicated

document.status gets updated but new document does not get replicated

there are no warning/errors of any sort.

If I go into studio, find that document and just click Save it will most likely get replicated properly (so far this worked every time when I knew which document was out of sync).

Any ideas on why this keeps happening and is there any way to get any sort of alert in a case like that. Right now the only way to tell is to actually write our own replication mechanism and compare or stumble upon document that didn't change statuses (for this particular case).

Thanks.

[Dominic Zukiewicz]

Vlad,

Can you paste your table definition (CREATE TABLE XXX) and your replication JSON, so we can diagnose it further?

Thanks

Dominic

[Oren Eini (Ayende Rahien)]

Also the version you are using.

Is it possible that you have both replications running concurrently and updating the same row?

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.

[Vlad Kosarev]

Dominic, can I send it to your email? I'd rather not post all of that here.

Oren, we enabled sql replication using stable right before 2916 (don't remember exact version), then we ran 2916 since it came out and now are on 2932, same behaviour. None of the replications update the same SQL table. Each replication has its own table to update. Two of them do use the same raven document type though. The two that have obvious issues both work against Order document.

[Dominic Zukiewicz]

Vlad,

You can rename your columns and amend your JSON to suit, if that helps?

Regards,

Dominic

--
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/Mwj4QdbZnsY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Do you have a way to repro this?

Can you on Skype with that?