[DOCS-408] Need documentation on how to downgrade a Replica Set Member into an Arbiter Created: 16/Aug/12  Updated: 30/Oct/23  Resolved: 11/Sep/12

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

Type: Task Priority: Major - P3
Reporter: Andre de Frere Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 11 years, 23 weeks, 1 day ago

 Description   

Customer could not find any information on how to change a regular member of a Replica Set into an Arbiter.

From the linked ticket, the following instructions were given:

Probably the safest way would be to start a new mongod in arbiter mode while the current mongod secondary is still running on the box. Once you have made sure the new arbiter is attached to the replica set and everything is running smoothly, you can shutdown the old secondary mongod. You will need to make sure the new process is starting on a different port to your old secondary.

One thing you will want to bear in mind is if you have your application connection string referencing the old secondary, you will need to remove this reference.



 Comments   
Comment by auto [ 11/Sep/12 ]

Author:

{u'date': u'2012-09-11T11:28:39-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: publishing DOCS-408
Branch: master
https://github.com/mongodb/docs/commit/3315b08c787fa67408da783bba173da20ef92db4

Comment by auto [ 11/Sep/12 ]

Author:

{u'date': u'2012-09-11T11:16:48-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-408 entered review edits to arbiter doc
Branch: master
https://github.com/mongodb/docs/commit/c90f1cb4d64645520a224160567f90a9d2700eef

Comment by Kristina Chodorow (Inactive) [ 11/Sep/12 ]

https://github.com/mongodb/docs/blob/master/draft/tutorial/convert-secondary-into-arbiter.txt#L61 - might be better to do this as step 1, there have been some sharding bugs around removing a member then shutting it down. However, theoretically they've all been fixed.

https://github.com/mongodb/docs/blob/master/draft/tutorial/convert-secondary-into-arbiter.txt#L71
https://github.com/mongodb/docs/blob/master/draft/tutorial/convert-secondary-into-arbiter.txt#L153 - these are a little weird, because drivers should automatically stop using the server. If you're connecting directly, you should probably modify your app before shutting down the server. I guess I'd move each of these up and say, "If your application is connecting directly to this server... do something."

Other than that, looks good!

Comment by Sam Kleinman (Inactive) [ 11/Sep/12 ]

https://github.com/mongodb/docs/blob/master/draft/tutorial/inserting-documents-into-a-sharded-collection.txt

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-09-06T10:36:58-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-408: edits
Branch: master
https://github.com/mongodb/docs/commit/ea5ce8d736fb9f35ccec6e3148eb3f56d7ef3fef

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-09-06T10:36:58-07:00', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-408: edits
Branch: master
https://github.com/mongodb/docs/commit/dfe02e21c2bd18ecf1b7f3c04ce4da8774c72769

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-09-06T10:29:03-07:00', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: merge: DOCS-408
Branch: master
https://github.com/mongodb/docs/commit/f070542bce8d0b843c28414efd5d40d5f9b080f0

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-08-28T13:44:57-07:00', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-408 proc to convert secondary to arbiter
Branch: master
https://github.com/mongodb/docs/commit/0985c96ee68469af8d2ea66d73af596f7e052c65

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-08-28T13:04:26-07:00', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-408 new proc to convert secondary to arbiter
Branch: master
https://github.com/mongodb/docs/commit/5051169fdf88a033319e6cc8bfffcccc757c5717

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-08-28T12:02:58-07:00', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-408 ongoing edits
Branch: master
https://github.com/mongodb/docs/commit/8ad3e7b18a0a972f194494f47c1e36714b9b19a0

Comment by auto [ 06/Sep/12 ]

Author:

{u'date': u'2012-08-28T08:47:06-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-408 change a secondary to an arbiter
Branch: master
https://github.com/mongodb/docs/commit/b4df9fe8d5e88a641cf40ade0687099f2b61574a

Comment by Bob Grabar [ 28/Aug/12 ]

https://github.com/mongodb/docs/pull/151

Comment by Sam Kleinman (Inactive) [ 16/Aug/12 ]

I think this is probably best served by an entry in the replica set FAQ, rather than a full fledged tutorial.

Generated at Thu Feb 08 07:38:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.