[SERVER-42059] Mongo replication sync halfway SocketException: remote: 192.168.168.122:27017 error: 9001 socket exception [RECV_ERROR] server [192.168.168.122:27017] Created: 03/Jul/19 Updated: 06/Dec/22 Resolved: 03/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Aaron Tai Wei Han | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Triage
|
| Participants: |
| Description |
|
I got one mongo v2.4.10 server with 1.7TB data, I am trying to migrate and upgrade the mongo to mongo v.3.0.15 server
I've setup a new mongo v.3.0.15 and configured replication for v3.0.15 to be secondary to sync with v.2.4.10 primary mongo.
The secondary was in STARTUP2 and the sync was almost finish as I can check with the growth of my storage device for the new machine which running mongo v.3.0.15
However there were some socket exceptions which caused both of my machine to resyn again from the start, just to ask anything I can configure or setup to prevent the error to happen again because I don't want to waste another 7 days to fail to sync up 1.7TB again.
Below are some logs from my mongo: Primary mongo (v2.4.10): ``` Secondary mongo (v.3.0.15) ... 2019-07-03T09:54:29.170+0800 W NETWORK [ReplExecNetThread-0] Failed to connect to 192.168.168.122:27017 after 1 milliseconds, giving up. ``` |
| Comments |
| Comment by Eric Sedor [ 03/Jul/19 ] |
|
Unfortunately we aren't able to assist with this process here. The SERVER project is for bugs and feature suggestions for active versions of the MongoDB server, and our support for MongoDB 3.0 ended in February 2018. For assistance troubleshooting in this case, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. |