-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.6.10
-
Component/s: Replication, WiredTiger
-
Labels:None
-
Environment:2.6.10 initial sync using 3.0.4 (WiredTiger) as the sync source
-
Replication
Currently, it's possible to perform initial sync of a 2.6 node using 3.0+WT as the source. The process finishes successfully without any errors in the logs. However, no indexes are cloned:
2015-06-29T17:36:59.844-0400 [rsSync] oplog sync 1 of 3 2015-06-29T17:36:59.844-0400 [rsSync] oplog sync 2 of 3 2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync building indexes 2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync cloning indexes for : test 2015-06-29T17:36:59.845-0400 [rsSync] oplog sync 3 of 3 2015-06-29T17:36:59.845-0400 [rsSync] replSet initial sync finishing up 2015-06-29T17:36:59.853-0400 [rsSync] replSet set minValid=5591b938:1 2015-06-29T17:36:59.858-0400 [rsSync] replSet RECOVERING 2015-06-29T17:36:59.858-0400 [rsSync] replSet initial sync done 2015-06-29T17:37:00.859-0400 [rsSync] replSet SECONDARY
While the documentation is very clear that in order to downgrade 3.0+WT you need to switch to 3.0+MMAP first, it's counter-intuitive that the initial sync process successfully completes in the above case while a critical piece of it has obviously failed. I would expect the initial sync process to error out.
-Alex