Doing some pre release testing or RavenDB Replication in build 960. Thought I’d log and share my results.
SetUp
- Create Two folders 8080 and 8081
- unzip code base into each one
- In server folder –> create plugins folder
- from bundles folder –> copy the dlls for –> replication, expiration
- copy in my custom replication conflict resolution dll
- edit server config -> change ‘get’ to ‘all’
- change port setting from * to 8080 and 8081 depending on which folder I’m in.
- Start Servers –> things look good.
- Testing
- Stop and start servers, look at logs.
Testing
I have a series of single task executable files I need to run. Some set up our environment, others push data.
Testing Create Tenants exe
- Run exe against server:8080 then server:8081
- Check to see if databases are there –> they are all good.
Replication Configuration and Testing
- Create a document Test/101 on server:8080, using the Silverlight tool.
- Configure Replication and Server:8081 –> follow help docs on RavenDB.net
- Wait a bit -> type reset in command line –> nothing happens –> 8081 is not reaching out to 8080 and pulling in the documents
- Configure replication on server 8080 to reach out to 8081
- Still no replication happening
- Added document Test/102 to 8081
- Found the error, copy and paste problem
- Checking logs after fixed typo
- Documents are still not replicating – Adding document test/105 to 8080
- Replication was working, but was replication from server:8080/databases/ClientA to server:8081 /databases/default
- Changed the Raven/Replication/Destinations documents on both servers to
{"Url": “http://dfrfrm025080:8080/databases/ClientA/”} - Success, Replication is working. Going to delete replicated records out of default database to prevent future confusion.
Replication Conflict Resolution Testing
- Turn off server:8081 –> using q command in console so I don’t get a bunch of index errors when I start again
- server:8080 edit Test/105 –> Change Name from “Jane” to “Tarzan” and Save
- Turn off server:8080
- start server:8081
- Make sure in ClientA database (database and tenant are about the same thing)
- Edit Test/105 –> change Name from “Jane” to “Superman” save
- Start Server:8080 and wait a bit for things to mesh
- Both documents say superman
- Now going to do the same thing but in reverse order, since the conflict resolution dll’s are installed on both servers.
- server:8081 test/105 – name “IronMan”
- server:8080 test/105 – name “Batman”
- Restarted both servers to speed things up
- Looks good now both say “Batman”
- Since I issued a restart, the test is not entirely valid, I’ll monitor this later when I start pushing large amounts of data.
No comments:
Post a Comment