[DOCS-9838] 3.2 docs for removing replica set member don't match 3.0 and 3.4 Created: 31/Jan/17 Updated: 17/Feb/23 Resolved: 17/Feb/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Johnny Shields | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 50 weeks, 5 days ago |
| Description |
|
The 3.2 docs for removing a replica set member: https://docs.mongodb.com/v3.2/tutorial/remove-replica-set-member/ have a different order of operations than 3.0 and 3.4 https://docs.mongodb.com/v3.0/tutorial/remove-replica-set-member/ I think the 3.2 docs might be incorrect, because when I followed that procedure the instances I removed became unresponsive. |
| Comments |
| Comment by Emet Ozar [ 17/Feb/23 ] |
|
See comments |
| Comment by Emet Ozar [ 17/Feb/23 ] |
|
Thanks kelsey.schubert@mongodb.com - will close as won't fix. |
| Comment by Kelsey Schubert [ 01/Feb/17 ] |
|
Hi johnnyshields, This isn't expected behavior. So we can investigate, would you please open a SERVER ticket with the logs of the affected mongod and the output from the mongo shell as it attempts to establish a connection? Thank you, |
| Comment by Johnny Shields [ 01/Feb/17 ] |
|
Yes, unable to connect via Mongo shell. |
| Comment by Ravind Kumar (Inactive) [ 31/Jan/17 ] |
|
Hello, Thanks for filing a DOCS ticket. While I look into this, can you go into detail as to what you mean by unresponsive instances? Is that to say that, after removing the mongod from the replica set, you were unable to connect to that member via the mongo shell, or a similar utility? |