The attached python file can be placed in testrunner/pytests
I'm then using the following ini file:
And the following config:
Note that this test is NOT using the normal XDCR test setup. Both servers are configured in the ini file as if it were one cluster, but they're never actually arranged that way. Also, the address of the second cluster is specified using a config parameter xdcr_host in the conf file. None of this is ideal for long-term testing, but happens to be what this test needs. And its the only thing we have to reproduce this behavior.
When I run this test on this cluster, the second cluster will have about 8500 (out of 9999) documents when the active vb reps drops to 0, and it then struggles to slowly replicate the remaining data from that point on.
Also, this isn't a true test, it just waits for 1 hour after setting up this scenario so you can watch it happen. After 1 hour, it will delete everything and record a passing test.