[DOCS-12003] Document process for converting arbiter to secondary Created: 28/Aug/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Nick Brewer Assignee: Ravind Kumar (Inactive)
Resolution: Won't Do Votes: 2
Labels: arbiter, conversion, replica-set, secondary
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-12004 Remove "Convert a Secondary to an Arb... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.5

 Description   

----------------------------

Original Description

The inverse of this is currently documented, but we are much more likely to suggest that a customer should convert an arbiter to a secondary, and so far the process for doing so is mostly taken from Google groups / stack overflow, where it varies between one of the following methods:

  • keep the existing arbiter, add a new secondary, then remove the arbiter
  • shut down the arbiter, update its configuration, add it as a secondary

It would be useful to document both, with a note that the right choice depends upon the level of risk the user is willing to incur.
----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 08:04:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.