RavenDB-TemporalVersioning icon indicating copy to clipboard operation
RavenDB-TemporalVersioning copied to clipboard

Published 20 hours ago • verified publisher icon mattjohnsonpint

Replication bundle compatibility

Open tunurgitr opened this issue 12 years ago • 4 comments
trafficstars

I'm using this with the replication bundle in a master/slave configuration -- I plan to use "ReadFromAllServers" set to true so I get read-striping.

I can see how a master/master configuration w/ TemporalVersioning could get complicated...so I'm avoiding that for now.

Currently, I am seeing the following issues/questions with what I'm trying to do:

  1. I'm assuming the TemporalVersioning bundle will need to be active on the master and slave DBs so that queries done on secondaries will work as expected. Could you verify that this is the recommended config?

  2. Looks like the "/{id}/temporalrevisions/{x}" documents are being replicated as expected (these documents are immutable, so I can't see having too many replication issues here). I noticed that these documents have the Replication meta-data attached, so everything there is working great.

  3. The status documents "/{id}/temporalhistory" are NOT being replicated correctly. They replicate one-time...but as changes are made, they are not updated on the secondaries. I noticed that it looks like they don't have replication metadata attached -- not sure if that's what's causing the issue.

Thanks again for your work on this bundle.

tunurgitr avatar Jan 19 '13 23:01 tunurgitr

I haven't done a whole lot with replication. I'll see what I can do. If you can put together some failing unit tests, that would be helpful. Perhaps one that replicates between two embedded databases.

mattjohnsonpint avatar Jan 20 '13 00:01 mattjohnsonpint

Oh, and the revision documents are almost immutable. Their metadata can still change, such as when revision 2 start date is copied to revision 1 until date, or when status changes, etc.

mattjohnsonpint avatar Jan 20 '13 01:01 mattjohnsonpint

Okay. Finally figured out what was going on...it's not this bundle. Thread on the groups is here: (https://groups.google.com/forum/?fromgroups=#!topic/ravendb/He7IFzxKKAs)

I haven't gone through other extensive tests, but I'll create new issues if I find any other problems that are specific to this bundle.

Thanks for your time.

tunurgitr avatar Jan 23 '13 13:01 tunurgitr

Interesting. Thanks for keeping me informed.

Yes, please let me know whether replication works or not. I think there may be issues with the temporal activator running on multiple servers. We should test setting a revision effective a few seconds in the future under both master/slave and master/master configurations. I have a feeling that when the activator kicks in, it will start a race condition between the replication sets.

mattjohnsonpint avatar Jan 23 '13 17:01 mattjohnsonpint