[SERVER-43355] stateStr" : "(not reachable/healthy) Created: 16/Sep/19 Updated: 16/Sep/19 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Uday Manne | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We have a 3 node replica set in PROD. Out of which PRIMARY and one of the SECONDARY are in (not reachable/healthy) state. So, promoted the SECONDARY which is available a PRIMARY using the below steps. https://docs.mongodb.com/manual/tutorial/reconfigure-replica-set-with-unavailable-members/
Unable to add the other 2 nodes to the replica set. Can you please help in bringing up the other nodes.
|
| Comments |
| Comment by Carl Champain (Inactive) [ 16/Sep/19 ] |
|
Hi manne@adobe.com, Thanks for the report. "Not reachable/unhealthy" is normally a network issue. Importantly, 3.2.1 version of MongoDB is already end-of-lifed, you should upgrade to the latest 4.2.0 or 4.0.12. The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Kind regards, |