Skip to content

DOCS-268 removed one option for replacing a replica set #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 6, 2012
Merged

DOCS-268 removed one option for replacing a replica set #176

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d837147
DOCS-268 removed one option for replacing a replica set
Sep 4, 2012
47cb759
DOCS-268 added a line break
Sep 4, 2012
527a3d0
DOCS-268 edits to proc for replacing a replica set
Sep 4, 2012
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 13 additions & 31 deletions source/administration/replica-sets.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,42 +129,24 @@ directly.
Replacing a Member
~~~~~~~~~~~~~~~~~~

There are two processes for replacing a member of a :term:`replica set`:
Use this procedure to replace a member of a replica set when the host
name has changed. This procedure preserves all existing configuration
for a member, except its hostname/location.

#. Remove and then re-add a member using the following procedure in
the :program:`mongo` shell:
Replacing a member is useful if you have an existing configuration
and only want to change the hostname of a member rather than completely
remove all configurations related to the existing/previous set member.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the following procedure to replace a member of a replica set when host names change. This operation preserves all existing configuration for a member, except its hostname/location.

Or something?


.. code-block:: javascript
Use :method:`rs.reconfig()` to change the value of the
:data:`members[n].host` field to reflect the new hostname or port
number. :method:`rs.reconfig()` will not change the value of :data:`members[n]._id`.

rs.remove("mongo2.example.net:27018")
rs.add({host: "mongo2.example.net:27019", priority: 0, hidden: true})

.. note::

The set member tracks its own replica set member ``_id``,
which can cause conflicts when trying to re-add a previous member.

To resolve this issue, you can either restart the
:program:`mongod` process on the member that you're re-adding, or
you can make sure that you specify an ``_id`` in the :method:`rs.add()`
document.

#. Use :method:`rs.reconfig()` to change the value of the
:data:`members[n].host` field to reflect the new hostname or port
number. In this case, the :data:`members[n]._id` field is not
reused by the new member.

.. code-block:: javascript

cfg = rs.conf()
cfg.members[0].host = "mongo2.example.net:27019"
rs.reconfig(cfg)
.. code-block:: javascript
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blank line before this line

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you add the blank line or should I?

On Tue, Sep 4, 2012 at 4:06 PM, Sam Kleinman [email protected]:

In source/administration/replica-sets.txt:

- reused by the new member.

- .. code-block:: javascript

  •  cfg = rs.conf()

  •  cfg.members[0].host = "mongo2.example.net:27019"

  •  rs.reconfig(cfg)
    +Replacing a member is useful if you have an existing configuration
    +and only want to change the hostname of a member rather than completely
    +remove all configurations related to the existing/previous set member.
    +
    +Use :method:rs.reconfig() to change the value of the
    +:data:members[n].host field to reflect the new hostname or port
    +number. The :data:members[n]._id field does not change as a result of this
    +operation.
    +.. code-block:: javascript

blank line before this line

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/176/files#r1527042.


The second method may be useful if you have an existing configuration
and only want to change the hostname of a member rather than
completely remove all configurations related to the existing/previous
set member. The :data:`members[n]._id` field does not change as a
result of this operation.
cfg = rs.conf()
cfg.members[0].host = "mongo2.example.net:27019"
rs.reconfig(cfg)

.. warning::

Expand Down