[SERVER-25432] Migrating using Replication - Issue with db authentication on new Replica Member Created: 03/Aug/16 Updated: 03/Aug/16 Resolved: 03/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | Mitchell Harding | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Our team is working on a migration from a clustered replica set mongo on AWS EC2 to a replica set cluster on Google's Compute Engine. We were able to add one of the new Google mongo instances as a member to the AWS cluster with a priority 0, however it appears that there is an issue with authentication which won't allow the new mongo to sync. Google Compute Instance:
AWS Primary Instance:
While checking the Google Compute Instance's mongo log, I see the following:
The Primary and other AWS instances seem to require authentication to be done through the 'admin' db, not 'local'. I'm assuming this is where the problem lies. Is there a way to have the new replica set member authenticate against admin, not local? |
| Comments |
| Comment by Ramon Fernandez Marina [ 03/Aug/16 ] |
|
mitchell@restorationmedia.com, I'm closing this ticket now, but please note that the configuration you're running is untested and unsupported – you need to be running 3.0 before you upgrade to 3.2. Even if the sync works you may have issues later on, so I'd strongly recommend you follow the documented upgrade procedures. Please note that the 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, where your question will reach a larger audience. In the future, a question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |
| Comment by Mitchell Harding [ 03/Aug/16 ] |
|
Hi Ramón, I actually figured out the issue related to the new node (version 3.2) and the old nodes (2.6) had issues with the schema version. We went ahead and just installed the same version on the new node and it seems to be syncing fine now. This ticket can be closed. |
| Comment by Ramon Fernandez Marina [ 03/Aug/16 ] |
|
mitchell@restorationmedia.com, what versions of MongoDB are running on each node? Also, can you please upload logs for the Google node as well as the current AWS primary from the last restart? Thanks, |