[SERVER-31353] Adding v3.0 member to v2.6 replica set Created: 02/Oct/17  Updated: 07/Nov/17  Resolved: 03/Oct/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.8, 3.0.0
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Jaan Paljasma Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I am trying to add new, hidden member (with version 3.0 running) to an existing replica set, which is running 2.6.8.

Host is added to replica set, connection is established, but synchronization won't start, and log output says:

2017-10-02T20:35:56.342+0000 F REPL     [rsSync] During initial sync, found documents in admin.system.users but could not find an auth schema version document in admin.system.version
2017-10-02T20:35:56.342+0000 F REPL     [rsSync] This indicates that the primary of this replica set was not successfully upgraded to schema version 3, which is the minimum supported schema version in this version of MongoDB

***aborting after fassert() failure

How to proceed?



 Comments   
Comment by Kelsey Schubert [ 03/Oct/17 ]

Hi jaan@hebsdigital.com,

I'd suggest reviewing the MongoDB 3.0 Upgrade Requirements. In particular, it appears that your authorization model needs to be upgraded.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Kelsey

Comment by Jaan Paljasma [ 03/Oct/17 ]

To add more context to it – our goal is to transfer our existing production replica set - which is still running on v2.6.8 - to Atlas, however, in order to get Live Migration working with MongoDB Atlas, the minimum requirement is v3.0 https://docs.atlas.mongodb.com/import/live-import/

Our plan was to add hidden RS member running in 3.0, and use this node to live migrate from. Any advise would be much appreciated.

Generated at Thu Feb 08 04:26:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.