Skip to content

DOCS-10235 remove old rs.remove() behaviour #2879

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

Closed
wants to merge 1 commit into from
Closed

DOCS-10235 remove old rs.remove() behaviour #2879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 3 additions & 8 deletions source/tutorial/remove-replica-set-member.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,9 +33,9 @@ Remove a Member Using ``rs.remove()``
rs.remove("mongod3.example.net:27017")
rs.remove("mongod3.example.net")

MongoDB disconnects the shell briefly as the replica set elects a
new primary. The shell then automatically reconnects. The
shell displays a ``DBClientCursor::init call() failed`` error even
MongoDB may disconnect the shell briefly if the replica set needs to elect a
new primary. The shell then automatically reconnects in such cases. The
shell may display a ``DBClientCursor::init call() failed`` error even
though the command succeeds.

.. _remove-member-using-reconfig:
Expand Down Expand Up @@ -110,11 +110,6 @@ here.

rs.reconfig(cfg)

As a result of :method:`rs.reconfig()` the shell will disconnect
while the replica set renegotiates which member is primary. The
shell displays a ``DBClientCursor::init call() failed`` error even
though the command succeeds, and will automatically reconnected.

#. To confirm the new configuration, issue :method:`rs.conf()`.

For the example above the output would be:
Expand Down