Description
When replication starts/restarts, and gets an error in the start up process, e.g., because of failure to retrieve start seqnos, it sometimes reports an error "Can't move update state from 0 to 1".
There are two issues:
1. The error message is incorrect. It should have been "from 0 to 2".
2. The error should not have been raised. It indicates a problem with state management in pipeline updater.
Attachments
For Gerrit Dashboard: MB-19181 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
62760,3 | MB-19181 fix invalid state transition in updater | master | goxdcr | Status: MERGED | +2 | +1 |
86536,3 | CBQE-4328: Automate MB-19181 and MB-21369 Change-Id: I938d1c66f5049dfc6b550fe7a4cbb6f3391344dd Reviewed-on: http://review.couchbase.org/86536 Tested-by: Arunkumar Senthilnathan <arun.couchbase@yahoo.com> Reviewed-by: Thuan Nguyen <soccon@gmail.com> | master | testrunner | Status: MERGED | +2 | +1 |
86538,2 | CBQE-4328: Automate MB-19181 and MB-21369 | spock | testrunner | Status: MERGED | +2 | +1 |
86540,2 | CBQE-4328: Automate MB-19181 and MB-21369 | watson | testrunner | Status: MERGED | +2 | +1 |