Details
-
Story
-
Resolution: Won't Fix
-
Critical
-
None
-
Security Level: Public
-
None
Description
Since we now can change parameter in test, I would like to add one more test into simple-test: failover/rebalance at destination cluster. Today we only have failover source node in simple-test, which misses a big set of code path handling destination topology change
This is critical and very easy to be broken by code change outside of my control (actually it was broken before and we spent > 1 week to recover).
You can either add one more xdcr test or, modify the current fail over test to include fail destination node.
This probably will increase simple-tets running time by another 2 minutes, but it may save us hours or even days of work by preventing buggy code from merging into kernel.
Please let me know what you think.
Thanks,
Junyi
On Oct 2, 2012, at 10:11 AM, Ketaki Gangal wrote:
Make simple-test ( commented out eperf stuff) and make xdcr-merge are stable at this point.
-Ketaki