Skip to content

Update 2.4-upgrade.txt #717

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

Update 2.4-upgrade.txt #717

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
14 changes: 7 additions & 7 deletions source/release-notes/2.4-upgrade.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,21 +143,21 @@ procedure.
processes, you may connect to a 2.2 :program:`mongos` process
and force the lock manually:

.. code-block:: sh
.. code-block:: sh

mongo <mongos.example.net>
mongo <mongos.example.net>

.. code-block:: javascript

db.getMongo().getCollection("config.locks").findOne({ _id : "upgradeLock" })
.. code-block:: javascript
db.getMongo().getCollection("config.locks").findOne({ _id : "upgradeLock" })

If the process specified in the ``process`` field of this document
is *verifiably* offline, run the following operation to force the
lock.

.. code-block:: javascript
.. code-block:: javascript

db.getMongo().getCollection("config.locks").update({ _id : "upgradeLock" }, { $set : { state : 0 } })
db.getMongo().getCollection("config.locks").update({ _id : "upgradeLock" }, { $set : { state : 0 } })

It is always more safe to wait for the :program:`mongos` to verify
that the lock is inactive, if you have any doubts about the
Expand Down