RavenDB Replication: Can I set a database's Raven-Replication-Source Guid manually? -


edit 2: i'm encountering precisely the same issue.

for ravendb replication, raven-replication-source guid handy when trying discern documents came server.

but in disaster recovery scenario, may necessary ensure instance's raven-replication-source guid remains same before failed.

my question:

  • can set database's raven-replication-source guid manually?

edit (in response ayende's comment):

and here scenario:

  • the client uses one master ravendb instance of reads , writes.
  • this master instance replicates hot spare instance.
  • when master instance fails, client fails on hot spare virtue of this configuration setting.
  • upon closer inspection, discover master ravendb instance has been corrupted , needs purged.
  • when recreate master ravendb instance, replication hot spare only replicate documents created on hot spare.
    • emphasis: hot spare not replicate documents created on master (prior disaster) master because raven-replication-source guid master's raven-replication-source guid.
  • and problem because, said, master ravendb instance purged, needed recreate database scratch, , need replicate all of documents hot spare master instance.

edit 3: @ayende's answer's pushed me discover solving wrong problem. here right way solve problem.

no, not control. , not sure scenario have requires this. raven-replication-source db id of last db changed (without replication).


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -