[SERVER-19224] 2.6 initial sync should fail if syncing from 3.0+WT Created: 29/Jun/15  Updated: 06/Dec/22  Resolved: 11/Nov/16

Status: Closed
Project: Core Server
Component/s: Replication, WiredTiger
Affects Version/s: 2.6.10
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

2.6.10 initial sync using 3.0.4 (WiredTiger) as the sync source


Issue Links:
Related
Assigned Teams:
Replication
Participants:

 Description   

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



 Comments   
Comment by Spencer Brody (Inactive) [ 11/Nov/16 ]

2.6 is EOL

Generated at Thu Feb 08 03:50:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.