[SERVER-52935] Failed to start node of Replica Set Created: 18/Nov/20 Updated: 23/Nov/20 Resolved: 23/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Giorgi Dvalishvili | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hello, MongoDB version v3.2.6
I have MongoDB Replica Set with 3 members (primary, secondary and arbiter). primary node failed and after failover secondary became primary. after that I tried to start mongod process on failed node and receiving following Error: "ERROR: child process failed, exited with error number 51".
there is content of log file:
I tried initial resync, too many hours, I receveid Error: W REPL [rsBackgroundSync] we are too stale to use hostname_pr_node:port_pr_node as a sync source
I tried change oplog size, but I have only two nodes (primary and arbiter) and I can't shutdown primary node. Thank you |
| Comments |
| Comment by Edwin Zhou [ 23/Nov/20 ] |
|
I’d first like to note that 3.2 has reached EOL in September 2018, and encourage you to upgrade to a supported version when you can. Resizing the oplog does not require a restart in later versions. You've attempted exactly what we would recommend for recovering from the first error. One option to perform an initial sync successfully may be to create a new node with greater resources (CPU/RAM), but we aren't able to advise about that here. The SERVER project is for reporting bugs and feature requests for supported MongoDB versions. Please ask our MongoDB Developer Community Forums about potential options for bringing back up the failed node. Downtime may or may not be necessary depending on your specific circumstances. Best, Edwin |