Skip to content

Commit 224958b

Browse files
npentrelandf-mongodb
authored andcommitted
DOCSP-8628: Document new 'hello' command
1 parent 1ea2a8f commit 224958b

20 files changed

+435
-33
lines changed

source/core/replica-set-hidden-member.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ data set but is **invisible** to client applications. Hidden members
1919
are good for workloads with different usage patterns from the other
2020
members in the :term:`replica set`. Hidden members must always be
2121
:ref:`priority 0 members <replica-set-secondary-only-members>` and
22-
so **cannot become primary**. The :method:`db.isMaster()` method does not
22+
so **cannot become primary**. The :method:`db.hello()` method does not
2323
display hidden members. Hidden members, however, **may vote** in
2424
:ref:`elections <replica-set-elections>`.
2525

source/core/sharded-cluster-query-router.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,15 +135,15 @@ Confirm Connection to ``mongos`` Instances
135135
------------------------------------------
136136

137137
To detect if the MongoDB instance that your client is connected
138-
to is :binary:`~bin.mongos`, use the :dbcommand:`isMaster` command. When a
139-
client connects to a :binary:`~bin.mongos`, :dbcommand:`isMaster` returns
138+
to is :binary:`~bin.mongos`, use the :dbcommand:`hello` command. When a
139+
client connects to a :binary:`~bin.mongos`, :dbcommand:`hello` returns
140140
a document with a ``msg`` field that holds the string
141141
``isdbgrid``. For example:
142142

143143
.. code-block:: javascript
144144

145145
{
146-
"ismaster" : true,
146+
"isWritablePrimary" : true,
147147
"msg" : "isdbgrid",
148148
"maxBsonObjectSize" : 16777216,
149149
"ok" : 1,

source/includes/fact-bulkwrite-operation-batches.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
The number of operations in each group cannot exceed the value of
22
the :limit:`maxWriteBatchSize <Write Command Batch Limit Size>` of
33
the database. As of MongoDB 3.6, this value is ``100,000``.
4-
This value is shown in the :data:`isMaster.maxWriteBatchSize` field.
4+
This value is shown in the :data:`hello.maxWriteBatchSize` field.
55

66
This limit prevents issues with oversized error messages. If a group
77
exceeds this :limit:`limit<Write Command Operation Limit Size>`,

source/reference/command.txt

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -394,9 +394,13 @@ Replication Commands
394394

395395
- Internal command that applies :term:`oplog` entries to the current data set.
396396

397+
* - :dbcommand:`hello`
398+
399+
- Displays information about this member's role in the replica set, including whether it is the primary.
400+
397401
* - :dbcommand:`isMaster`
398402

399-
- Displays information about this member's role in the replica set, including whether it is the master.
403+
- *Deprecated*. Use :dbcommand:`hello` instead.
400404

401405
* - :dbcommand:`replSetAbortPrimaryCatchUp`
402406

0 commit comments

Comments
 (0)