@@ -479,4 +479,39 @@ content: |
479479 :ref:`forceJumbo <movechunk-forceJumbo>` to allow for the
480480 migration of chunks that are too large to move. The chunks may or
481481 may not be labeled :ref:`jumbo <jumbo-chunk>`.
482+ ---
483+ ref : 4.4-changes-repl-state-restrictions
484+ content : |
485+
486+ Starting in MongoDB 4.4, to run on a replica set member, the
487+ following operations require the member to be in
488+ :replstate:`PRIMARY` or :replstate:`SECONDARY` state.
489+
490+ - :dbcommand:`listDatabases`
491+ - :dbcommand:`listCollections`
492+ - :dbcommand:`listIndexes`
493+ - :dbcommand:`distinct`
494+ - :dbcommand:`dbStats`
495+ - :dbcommand:`collStats`
496+
497+ If the member is in another state, such as :replstate:`STARTUP2`,
498+ the operation errors.
499+
500+ In previous versions, the operations can also be run when the member
501+ is in :replstate:`STARTUP2`. However, the operations wait
502+ until the member transitions to :replstate:`RECOVERING`.
503+
504+ ---
505+ ref : 4.4-changes-repl-state-restrictions-operation
506+ content : |
507+
508+ Starting in MongoDB 4.4, to run on a replica set member,
509+ |operations| operations require the member to be in
510+ :replstate:`PRIMARY` or :replstate:`SECONDARY` state. If the member
511+ is in another state, such as :replstate:`STARTUP2`, the
512+ operation errors.
513+
514+ In previous versions, the operations can also be run when the member
515+ is in :replstate:`STARTUP2`. However, the operations wait
516+ until the member transitions to :replstate:`RECOVERING`.
482517 ...
0 commit comments