SERVER-42846 Update manpages

14 files changed, 5742 insertions, 1113 deletions

diff --git a/debian/bsondump.1 b/debian/bsondump.1
index 46b2d0dd02d..dbb3bb31985 100644
--- a/debian/bsondump.1
+++ b/debian/bsondump.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "BSONDUMP" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "BSONDUMP" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 bsondump \- MongoDB BSON Utility
 .
@@ -35,6 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
 \fI\%Options\fP
 .IP \(bu 2
 \fI\%Examples\fP
@@ -62,6 +64,32 @@ Run \fI\%bsondump\fP from the system command line, not the \fBmongo\fP shell.
 BSON files, not a tool for data ingestion or other application use.
 .UNINDENT
 .UNINDENT
+.sp
+Starting in version 4.2, \fI\%bsondump\fP uses Extended
+JSON v2.0 (Canonical mode)
+to format its data.
+.SH AVAILABILITY
+.sp
+The \fI\%bsondump\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
 .SH OPTIONS
 .sp
 Changed in version 3.0.0: \fI\%bsondump\fP removed the \fB\-\-filter\fP, \fB\-\-dbpath\fP and the
@@ -116,7 +144,7 @@ For objects with a high degree of sub\-document nesting,
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-type <=json|=debug>
+.B \-\-type=<json|debug>
 Changes the operation of \fBbsondump\fP from outputting
 "JSON" (the default) to a debugging format.
 .UNINDENT
@@ -148,7 +176,7 @@ BSON\&. This data is typically generated by
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-outFile
+.B \-\-outFile=<file>
 New in version 3.4.
 
 .sp
@@ -170,7 +198,7 @@ create corresponding JSON files, you can use the
 .sp
 .nf
 .ft C
-bsondump \-\-outFile collection.json collection.bson
+bsondump \-\-outFile=collection.json collection.bson
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongo.1 b/debian/mongo.1
index e06ce6b7020..f5a90531131 100644
--- a/debian/mongo.1
+++ b/debian/mongo.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGO" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGO" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongo \- MongoDB Shell
 .
@@ -54,16 +54,43 @@ MongoDB, which provides a powerful interface for system
 administrators as well as a way for developers to test queries and
 operations directly with the database. \fI\%mongo\fP also provides
 a fully functional JavaScript environment for use with a MongoDB.
-The \fI\%mongo\fP shell is part of the \fI\%MongoDB distributions\fP\&.
+.sp
+The \fI\%mongo\fP shell is included as part of the MongoDB Server installation. MongoDB also provides the \fI\%mongo\fP
+shell as a standalone package. To download the standalone \fI\%mongo\fP
+shell package:
+.INDENT 0.0
+.IP 1. 3
+Open the \fI\%Download Center\fP\&. For the
+\fI\%mongo\fP Enterprise Shell, select the
+MongoDB Enterprise Server tab.
+.IP 2. 3
+Select your preferred Version and OS from the
+dropdowns.
+.IP 3. 3
+Select \fBShell\fP from the Package dropdown and click
+Download to start downloading the package.
+.sp
+If the \fBShell\fP option is unavailable for the selected OS and
+Version, contact MongoDB technical\-support for assistance.
+.UNINDENT
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+Starting in MongoDB 4.2 (and 4.0.13), the \fI\%mongo\fP shell displays a
+warning message when connected to non\-genuine MongoDB instances as
+these instances may behave differently from the official MongoDB
+instances; e.g. missing or incomplete features, different feature
+behaviors, etc.
+.IP \(bu 2
 Starting in version 4.0, \fI\%mongo\fP disables support for TLS 1.0
 encryption on systems where TLS 1.1+ is available. For
 more details, see 4.0\-disable\-tls\&.
 .UNINDENT
 .UNINDENT
+.UNINDENT
 .SH SYNTAX
 .INDENT 0.0
 .IP \(bu 2
@@ -587,6 +614,15 @@ default name of \fBmongodb\fP\&.
 This option is available only in MongoDB Enterprise.
 .UNINDENT
 .SS TLS Options
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Starting in version 4.0, \fI\%mongo\fP disables support for TLS 1.0
+encryption on systems where TLS 1.1+ is available. For
+more details, see 4.0\-disable\-tls\&.
+.UNINDENT
+.UNINDENT
 .INDENT 0.0
 .INDENT 3.5
 .SS See
@@ -745,8 +781,6 @@ authentication.
 .UNINDENT
 .UNINDENT
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -883,6 +917,15 @@ counterparts instead. The SSL protocol is deprecated and MongoDB
 supports TLS 1.0 and later.
 .UNINDENT
 .UNINDENT
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Starting in version 4.0, \fI\%mongo\fP disables support for TLS 1.0
+encryption on systems where TLS 1.1+ is available. For
+more details, see 4.0\-disable\-tls\&.
+.UNINDENT
+.UNINDENT
 .INDENT 0.0
 .TP
 .B \-\-ssl
@@ -1085,8 +1128,6 @@ authentication.
 .UNINDENT
 .UNINDENT
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -1171,6 +1212,98 @@ Enables retryable writes as the default for sessions in the
 .sp
 For more information on sessions, see sessions\&.
 .UNINDENT
+.SS Client\-Side Field Level Encryption Options
+.INDENT 0.0
+.TP
+.B \-\-awsAccessKeyId <string>
+An AWS \fI\%Access Key\fP
+associated to an IAM user with \fBList\fP and \fBRead\fP permissions for the
+AWS Key Management Service (KMS). The \fBmongo\fP shell uses the specified
+\fI\%\-\-awsAccessKeyId\fP to access the KMS.
+.sp
+\fI\%\-\-awsAccessKeyId\fP is required for enabling /core/security\-client\-side\-encryption
+for the \fBmongo\fP shell session. \fI\%\-\-awsAccessKeyId\fP requires \fIall\fP of the following
+command line options:
+.INDENT 7.0
+.IP \(bu 2
+\fI\%\-\-awsSecretAccessKey\fP
+.IP \(bu 2
+\fI\%\-\-keyVaultNamespace\fP
+.UNINDENT
+.sp
+If \fI\%\-\-awsAccessKeyId\fP is omitted, use the \fBMongo()\fP constructor within the shell
+session to enable client\-side field level encryption.
+.sp
+To mitigate the risk of leaking access keys into logs, consider specifying
+an environmental variable to \fI\%\-\-awsAccessKeyId\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-awsSecretAccessKey <string>
+An AWS \fI\%Secret Key\fP
+associated to the specified \fI\%\-\-awsAccessKeyId\fP\&.
+.sp
+\fI\%\-\-awsSecretAccessKey\fP is required for enabling /core/security\-client\-side\-encryption
+for the \fBmongo\fP shell session. \fI\%\-\-awsSecretAccessKey\fP requires \fIall\fP of the following
+command line options:
+.INDENT 7.0
+.IP \(bu 2
+\fI\%\-\-awsAccessKeyId\fP
+.IP \(bu 2
+\fI\%\-\-keyVaultNamespace\fP
+.UNINDENT
+.sp
+If \fI\%\-\-awsSecretAccessKey\fP and its supporting options are omitted, use \fBMongo()\fP
+within the shell session to enable client\-side field level encryption.
+.sp
+To mitigate the risk of leaking access keys into logs, consider specifying
+an environmental variable to \fI\%\-\-awsSecretAccessKey\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-awsSessionToken <string>
+An AWS \fI\%Session Token\fP
+associated to the specified \fI\%\-\-awsAccessKeyId\fP\&.
+.sp
+\fI\%\-\-awsSessionToken\fP is required for enabling /core/security\-client\-side\-encryption
+for the \fBmongo\fP shell session. \fI\%\-\-awsSessionToken\fP requires \fIall\fP of the following
+command line options:
+.INDENT 7.0
+.IP \(bu 2
+\fI\%\-\-awsAccessKeyId\fP
+.IP \(bu 2
+\fI\%\-\-awsSecretAccessKey\fP
+.IP \(bu 2
+\fI\%\-\-keyVaultNamespace\fP
+.UNINDENT
+.sp
+If \fI\%\-\-awsSessionToken\fP and its supporting options are omitted, use \fBMongo()\fP
+within the shell session to enable client\-side field level encryption.
+.sp
+To mitigate the risk of leaking access keys into logs, consider specifying
+an environmental variable to \fI\%\-\-awsSessionToken\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-keyVaultNamespace <string>
+The full namespace (\fB<database>.<collection>\fP) of the collection used as a
+key vault for /core/security\-client\-side\-encryption\&. \fI\%\-\-keyVaultNamespace\fP is
+required for enabling client\-side field level encryption. for the \fBmongo\fP
+shell session. \fBmongo\fP creates the specified namespace if it does not
+exist.
+.sp
+\fI\%\-\-keyVaultNamespace\fP requires \fIall\fP of the following command line options:
+.INDENT 7.0
+.IP \(bu 2
+\fI\%\-\-awsAccessKeyId\fP
+.IP \(bu 2
+\fI\%\-\-awsSecretAccessKey\fP
+.UNINDENT
+.sp
+If \fI\%\-\-keyVaultNamespace\fP and its supporting options are omitted, use the \fBMongo()\fP
+constructor within the shell session to enable client\-side field level
+encryption.
+.UNINDENT
 .SH FILES
 .INDENT 0.0
 .TP
@@ -1650,10 +1783,23 @@ mongo script\-file.js \-u <user> \-p
 .fi
 .UNINDENT
 .UNINDENT
-.SS Use \fI\%\-\-eval\fP to Print Query Results as JSON
 .sp
-To print return a query as JSON, from the system prompt using
-the \fI\%\-\-eval\fP option, use the following form:
+\fBSEE ALSO:\fP
+.INDENT 0.0
+.INDENT 3.5
+\fBisInteractive()\fP
+.UNINDENT
+.UNINDENT
+.SS Use \fI\%\-\-eval\fP to Execute JavaScript Code
+.sp
+You may use the \fI\%\-\-eval\fP option to execute
+JavaScript directly from the command line.
+.sp
+For example, the following operation evaluates a JavaScript string
+which queries a collection and prints the results as JSON.
+.sp
+On Linux and macOS, you will need to use single quotes (e.g. \fB\(aq\fP)
+to enclose the JavaScript, using the following form:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -1665,8 +1811,18 @@ mongo \-\-eval \(aqdb.collection.find().forEach(printjson)\(aq
 .UNINDENT
 .UNINDENT
 .sp
-Use single quotes (e.g. \fB\(aq\fP) to enclose the JavaScript, as well as
-the additional JavaScript required to generate this output.
+On Windows, you will need to use double quotes (e.g. \fB"\fP)
+to enclose the JavaScript, using the following form:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongo \-\-eval "db.collection.find().forEach(printjson)"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
 \fBSEE ALSO:\fP
 .INDENT 0.0
@@ -1678,6 +1834,8 @@ the additional JavaScript required to generate this output.
 /reference/method
 .IP \(bu 2
 /mongo
+.IP \(bu 2
+\fBisInteractive()\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
diff --git a/debian/mongod.1 b/debian/mongod.1
index 5da79eb7515..026c6c849d4 100644
--- a/debian/mongod.1
+++ b/debian/mongod.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOD" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOD" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongod \- MongoDB Server
 .
@@ -387,6 +387,45 @@ is, you can specify one or the other, but not both.
 .UNINDENT
 .INDENT 0.0
 .TP
+.B \-\-clusterIpSourceWhitelist <string>
+New in version 3.6.
+
+.sp
+A list of IP addresses/CIDR (\fI\%Classless Inter\-Domain Routing\fP) ranges against which the
+\fI\%mongod\fP validates authentication requests from other members of
+the replica set and, if part of a sharded cluster, the \fBmongos\fP
+instances. The \fI\%mongod\fP verifies that the originating IP is
+either explicitly in the list or belongs to a CIDR range in the list. If the
+IP address is not present, the server does not authenticate the
+\fI\%mongod\fP or \fBmongos\fP\&.
+.sp
+\fI\%\-\-clusterIpSourceWhitelist\fP has no effect on a \fI\%mongod\fP started without
+authentication\&.
+.sp
+\fI\%\-\-clusterIpSourceWhitelist\fP accepts multiple comma\-separated IPv4/6 addresses or Classless
+Inter\-Domain Routing (\fI\%CIDR\fP) ranges:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-clusterIpSourceWhitelist 192.0.2.0/24,127.0.0.1,::1
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBIMPORTANT:\fP
+.INDENT 7.0
+.INDENT 3.5
+Ensure \fI\%\-\-clusterIpSourceWhitelist\fP includes the IP address \fIor\fP CIDR ranges that include the
+IP address of each replica set member or \fBmongos\fP in the
+deployment to ensure healthy communication between cluster components.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
 .B \-\-ipv6
 Enables IPv6 support. \fBmongod\fP disables IPv6 support by default.
 .sp
@@ -602,11 +641,33 @@ For internal diagnostic use only.
 .INDENT 0.0
 .TP
 .B \-\-pidfilepath <path>
-Specifies a file location to hold the process ID of the \fBmongod\fP
-process where \fBmongod\fP will write its PID. This is useful for
-tracking the \fBmongod\fP process in combination with
-the \fI\%\-\-fork\fP option. Without a specified \fI\%\-\-pidfilepath\fP option, the
-process creates no PID file.
+Specifies a file location to store the process ID (PID) of the \fBmongod\fP
+process . The user running the the \fBmongod\fP or \fBmongos\fP
+process must be able to write to this path. If the \fI\%\-\-pidfilepath\fP option is not
+specified, the process does not create a PID file. This option is generally
+only useful in combination with the the \fI\%\-\-fork\fP option.
+.INDENT 7.0
+.INDENT 3.5
+.IP "Linux"
+.sp
+On Linux, PID file management is generally the responsibility of
+your distro\(aqs init system: usually a service file in the \fB/etc/init.d\fP
+directory, or a systemd unit file registered with \fBsystemctl\fP\&. Only
+use the \fI\%\-\-pidfilepath\fP option if you are not using one of these init
+systems. For more information, please see the respective
+Installation Guide for your operating system.
+.UNINDENT
+.UNINDENT
+.INDENT 7.0
+.INDENT 3.5
+.IP "macOS"
+.sp
+On macOS, PID file management is generally handled by \fBbrew\fP\&. Only use
+the \fI\%\-\-pidfilepath\fP option if you are not using \fBbrew\fP on your macOS system.
+For more information, please see the respective
+Installation Guide for your operating system.
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -700,6 +761,8 @@ background. By default \fBmongod\fP does not run as a daemon:
 typically you will run \fBmongod\fP as a daemon, either by using
 \fI\%\-\-fork\fP or by using a controlling process that handles the
 daemonization process (e.g. as with \fBupstart\fP and \fBsystemd\fP).
+.sp
+The \fI\%\-\-fork\fP option is not supported on Windows.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -978,12 +1041,26 @@ _
 New in version 4.2.
 
 .sp
-Outputs the resolved YAML configuration document for the \fBmongod\fP
-to \fBstdout\fP and halts the \fBmongod\fP instance. For configuration
-options using externally\-sourced\-values, \fI\%\-\-outputConfig\fP returns the
-resolved value for those options. This may include any configured
-passwords or secrets previously obfuscated through the external
-source.
+Outputs the \fBmongod\fP instance\(aqs configuration options, formatted
+in YAML, to \fBstdout\fP and exits the \fBmongod\fP instance. For
+configuration options that uses externally\-sourced\-values,
+\fI\%\-\-outputConfig\fP returns the resolved value for those options.
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+This may include any configured passwords or secrets previously
+obfuscated through the external source.
+.UNINDENT
+.UNINDENT
+.sp
+For usage examples, see:
+.INDENT 7.0
+.IP \(bu 2
+expansion\-directive\-output
+.IP \(bu 2
+/tutorial/convert\-command\-line\-options\-to\-yaml
+.UNINDENT
 .UNINDENT
 .SS Free Monitoring
 .sp
@@ -1061,14 +1138,14 @@ For the corresponding configuration file setting, see
 New in version 3.4: Available in MongoDB Enterprise only.
 
 .sp
-The LDAP server against which the \fBmongod\fP executes LDAP operations
-against to authenticate users or determine what actions a user is authorized
-to perform on a given database. If the LDAP server specified has any
-replicated instances, you may specify the host and port of each replicated
-server in a comma\-delimited list.
+The LDAP server against which the \fBmongod\fP authenticates users or
+determines what actions a user is authorized to perform on a given
+database. If the LDAP server specified has any replicated instances,
+you may specify the host and port of each replicated server in a
+comma\-delimited list.
 .sp
-If your LDAP infrastrucure partitions the LDAP directory over multiple LDAP
-servers, specify \fIone\fP LDAP server any of its replicated instances to
+If your LDAP infrastructure partitions the LDAP directory over multiple LDAP
+servers, specify \fIone\fP LDAP server or any of its replicated instances to
 \fI\%\-\-ldapServers\fP\&. MongoDB supports following LDAP referrals as defined in \fI\%RFC 4511
 4.1.10\fP\&. Do not use \fI\%\-\-ldapServers\fP
 for listing every LDAP server in your infrastructure.
@@ -1504,8 +1581,35 @@ A relative LDAP query URL formatted conforming to \fI\%RFC4515\fP and \fI\%RFC45
 the LDAP groups to which the authenticated user belongs to. The query is
 relative to the host or hosts specified in \fI\%\-\-ldapServers\fP\&.
 .sp
-Use the \fB{USER}\fP placeholder in the URL to substitute the authenticated
-username, or the transformed username if a \fI\%username mapping\fP is specified.
+In the URL, you can use the following substituion tokens:
+.TS
+center;
+|l|l|.
+_
+T{
+Substitution Token
+T}	T{
+Description
+T}
+_
+T{
+\fB{USER}\fP
+T}	T{
+Substitutes the authenticated username, or the
+\fBtransformed\fP
+username if a \fI\%username mapping\fP is specified.
+T}
+_
+T{
+\fB{PROVIDED_USER}\fP
+T}	T{
+Substitutes the supplied username, i.e. before either
+authentication or \fBLDAP transformation\fP\&.
+.sp
+New in version 4.2.
+T}
+_
+.TE
 .sp
 When constructing the query URL, ensure that the order of LDAP parameters
 respects RFC4516:
@@ -1688,47 +1792,6 @@ in\-memory storage engine\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-nssize <value>
-\fIDefault\fP: 16
-.sp
-Specifies the default size for namespace files, which are files that end
-in \fB\&.ns\fP\&. Each collection and index counts as a namespace.
-.sp
-Use this setting to control size for newly created namespace files. This
-option has no impact on existing files. The maximum size for a namespace
-file is 2047 megabytes. The default value of 16 megabytes provides for
-approximately 24,000 namespaces.
-.UNINDENT
-.INDENT 0.0
-.TP
-.B \-\-quota
-Enables a maximum limit for the number data files each database can
-have. When running with the \fI\%\-\-quota\fP option, MongoDB has a maximum of 8
-data files per database. Adjust the quota with
-\fI\%\-\-quotaFiles\fP\&.
-.UNINDENT
-.INDENT 0.0
-.TP
-.B \-\-quotaFiles <number>
-\fIDefault\fP: 8
-.sp
-Modifies the limit on the number of data files per database. \fI\%\-\-quotaFiles\fP
-option requires that you set \fI\%\-\-quota\fP\&.
-.UNINDENT
-.INDENT 0.0
-.TP
-.B \-\-smallfiles
-Sets MongoDB to use a smaller default file size. The \fI\%\-\-smallfiles\fP option
-reduces the initial size for data files and limits the maximum size to
-512 megabytes. \fI\%\-\-smallfiles\fP also reduces the size of each journal
-file from 1 gigabyte to 128 megabytes. Use \fI\%\-\-smallfiles\fP if you have a large
-number of databases that each holds a small quantity of data.
-.sp
-The \fI\%\-\-smallfiles\fP option can lead the \fBmongod\fP instance to create a large
-number of files, which can affect performance for larger databases.
-.UNINDENT
-.INDENT 0.0
-.TP
 .B \-\-syncdelay <value>
 \fIDefault\fP: 60
 .sp
@@ -1843,11 +1906,11 @@ If any voting member of a replica set uses the in\-memory
 storage engine, you must set
 \fBwriteConcernMajorityJournalDefault\fP to \fBfalse\fP\&.
 .sp
-Starting in version 4.2, if a replica set member uses the
-in\-memory storage engine (voting or
-non\-voting) but the replica set has
-\fBwriteConcernMajorityJournalDefault\fP set to true, the replica set member
-logs a startup warning.
+Starting in version 4.2 (and 4.0.13 and 3.6.14 ), if a replica set
+member uses the in\-memory storage engine
+(voting or non\-voting) but the replica set has
+\fBwriteConcernMajorityJournalDefault\fP set to true, the
+replica set member logs a startup warning.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1864,21 +1927,9 @@ WiredTiger storage engine.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-journalOptions <arguments>
-Provides functionality for testing. Not for general use, and will affect data
-file integrity in the case of abnormal system shutdown.
-.sp
-Not available for \fI\%mongod\fP instances that use the
-in\-memory storage engine\&.
-.UNINDENT
-.INDENT 0.0
-.TP
 .B \-\-journalCommitInterval <value>
 \fIDefault\fP: 100 or 30
 .sp
-Changed in version 3.2.
-
-.sp
 The maximum amount of time in milliseconds that
 the \fBmongod\fP process allows between
 journal operations. Values can range from 1 to 500 milliseconds. Lower
@@ -1890,6 +1941,13 @@ a write with \fBj:true\fP will cause an immediate sync of the journal.
 .sp
 Not available for \fI\%mongod\fP instances that use the
 in\-memory storage engine\&.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Known Issue in 4.2.0: The \fI\%\-\-journalCommitInterval\fP is missing in 4.2.0.
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .SS WiredTiger Options
 .INDENT 0.0
@@ -1898,10 +1956,8 @@ in\-memory storage engine\&.
 Defines the maximum size of the internal cache that WiredTiger will
 use for all data. The memory consumed by an index build (see
 \fBmaxIndexBuildMemoryUsageMegabytes\fP) is separate from the
-WiredTiger cache memory.
-.sp
-Starting in MongoDB 3.4, \fI\%\-\-wiredTigerCacheSizeGB\fP values can range from 0.25 GB  to
-10000 GB and can be a float.
+WiredTiger cache memory. Starting in MongoDB 3.4, the values can range
+from 0.25 GB  to 10000 GB and can be a float.
 .sp
 Starting in MongoDB 3.4, the default WiredTiger internal cache size is
 the larger of either:
@@ -1918,6 +1974,18 @@ Conversely, a system with a total of 1.25 GB of RAM will allocate 256
 MB to the WiredTiger cache because that is more than half of the
 total RAM minus one gigabyte (\fB0.5 * (1.25 GB \- 1 GB) = 128 MB < 256 MB\fP).
 .sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+In some instances, such as when running in a container, the database
+can have memory constraints that are lower than the total system
+memory. In such instances, this memory limit, rather than the total
+system memory, is used as the maximum RAM available.
+.sp
+To see the memory limit, see \fBhostInfo.system.memLimitMB\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
 Avoid increasing the WiredTiger internal cache size above its
 default value.
 .sp
@@ -1950,9 +2018,50 @@ instances.
 .sp
 If you run \fI\%mongod\fP in a container (e.g. \fBlxc\fP,
 \fBcgroups\fP, Docker, etc.) that does \fInot\fP have access to all of the
-RAM available in a system, you must set \fI\%\-\-wiredTigerCacheSizeGB\fP to a value less
-than the amount of RAM available in the container. The exact amount
-depends on the other processes running in the container.
+RAM available in a system, you must set \fI\%\-\-wiredTigerCacheSizeGB\fP to a value
+less than the amount of RAM available in the container. The exact
+amount depends on the other processes running in the container. See
+\fBmemLimitMB\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-wiredTigerMaxCacheOverflowFileSizeGB <float>
+Specifies the maximum size (in GB) for the "lookaside (or cache
+overflow) table" file \fBWiredTigerLAS.wt\fP\&.
+.sp
+The setting can accept the following values:
+.TS
+center;
+|l|l|.
+_
+T{
+Value
+T}	T{
+Description
+T}
+_
+T{
+\fB0\fP
+T}	T{
+The default value. If set to \fB0\fP, the file size is
+unbounded.
+T}
+_
+T{
+number >= 0.1
+T}	T{
+The maximum size (in GB). If the \fBWiredTigerLAS.wt\fP
+file exceeds this size, \fI\%mongod\fP exits with a
+fatal assertion. You can clear the \fBWiredTigerLAS.wt\fP
+file and restart \fI\%mongod\fP\&.
+T}
+_
+.TE
+.sp
+To change the maximum size during runtime, use the
+\fBwiredTigerMaxCacheOverflowSizeGB\fP parameter.
+.sp
+\fIAvailable starting in MongoDB 4.2.1 (and 4.0.12)\fP
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -3949,6 +4058,25 @@ need to, but can, also specify the \fI\%\-\-kmipServerCAFile\fP\&.
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-eseDatabaseKeyRollover
+New in version 4.2.
+
+.sp
+Roll over the encrypted storage engine database keys configured with
+\fBAES256\-GCM\fP cipher.
+.sp
+When \fI\%mongod\fP instance is started with this option, the
+instance rotates the keys and exits.
+.INDENT 7.0
+.INDENT 3.5
+.IP "Enterprise Feature"
+.sp
+Available in MongoDB Enterprise only.
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SH AUTHOR
 MongoDB Documentation Project
 .SH COPYRIGHT
diff --git a/debian/mongodb-parameters.5 b/debian/mongodb-parameters.5
index 729c7e1191d..e0f4a468db1 100644
--- a/debian/mongodb-parameters.5
+++ b/debian/mongodb-parameters.5
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGODB-PARAMETERS" "5" "Jun 21, 2018" "4.0" "mongodb-manual"
+.TH "MONGODB-PARAMETERS" "5" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongodb-parameters \- MongoDB setParameter Options
 .
@@ -274,23 +274,219 @@ Defaults to 30 seconds.
 .UNINDENT
 .INDENT 0.0
 .TP
+.B ldapUseConnectionPool
+New in version 4.0.9.
+
+.sp
+Specifies whether MongoDB should use connection pooling when
+connecting to the LDAP server for authentication/authorization.
+.sp
+\fBStarting in version 4.2\fP, MongoDB uses the following default values:
+.INDENT 7.0
+.IP \(bu 2
+true on Windows.
+.IP \(bu 2
+true on Linux where MongoDB Enterprise binaries are linked against
+\fBlibldap_r\fP\&.
+.IP \(bu 2
+false on Linux where MongoDB Enterprise binaries are linked against
+\fBlibldap\fP\&.
+.INDENT 2.0
+.INDENT 3.5
+.SS Tip
+.sp
+To allow concurrent authentication commands for LDAP users, you
+may wish to link to \fBlibldap_r\fP\&. For assistance, contact
+support\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBIn earlier versions (versions 4.0.9+)\fP, the default value is
+\fBfalse\fP\&.
+.sp
+You can only set \fI\%ldapUseConnectionPool\fP during
+start\-up, and cannot change this setting with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolUseLatencyForHostPriority
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+\fIDefault\fP: true
+.sp
+A boolean that determines whether the LDAP connection pool (see
+\fI\%ldapUseConnectionPool\fP) should use latency of the LDAP
+servers to determine the connection order (from lowest latency to
+highest).
+.sp
+You can only set
+\fI\%ldapConnectionPoolUseLatencyForHostPriority\fP during
+start\-up, and cannot change this setting during runtime with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolMinimumConnectionsPerHost
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+\fIDefault\fP: 1
+.sp
+The minimum number of connections to keep open to each LDAP server.
+.sp
+You can only set
+\fI\%ldapConnectionPoolMinimumConnectionsPerHost\fP during
+start\-up, and cannot change this setting during runtime with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolMaximumConnectionsPerHost
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+The maximum number of connections to keep open to each LDAP server.
+.sp
+You can only set
+\fI\%ldapConnectionPoolMaximumConnectionsPerHost\fP during
+start\-up, and cannot change this setting during runtime with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolMaximumConnectionsInProgressPerHost
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+The maximum number of in\-progress connect operations to each LDAP server.
+.sp
+You can only set
+\fI\%ldapConnectionPoolMaximumConnectionsInProgressPerHost\fP
+during start\-up, and cannot change this setting with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolHostRefreshIntervalMillis
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+\fIDefault\fP: 60000
+.sp
+The number of milliseconds in\-between health checks of the pooled
+LDAP connections.
+.sp
+You can only set
+\fI\%ldapConnectionPoolHostRefreshIntervalMillis\fP during
+start\-up, and cannot change this setting with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ldapConnectionPoolIdleHostTimeoutSecs
+\fINew in version 4.2.1 and 4.0.13\fP
+.sp
+\fIDefault\fP: 300
+.sp
+The maximum number of seconds that the pooled connections to an LDAP
+server can remain idle before being closed.
+.sp
+You can only set
+\fI\%ldapConnectionPoolIdleHostTimeoutSecs\fP during
+start\-up, and cannot change this setting with the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
 .B opensslCipherConfig
 New in version 3.6.
 
 .sp
+Changed in version 4.0: With the use of native TLS/SSL libraries, the parameter
+\fI\%opensslCipherConfig\fP is supported for Linux/BSD and
+no longer supported in Windows and macOS. See MongoDB 4.0
+TLS/SSL\&.
+
+.sp
 Specify the cipher string for OpenSSL when using TLS/SSL encryption.
 For a list of cipher strings, see
-\fI\%https://wiki.openssl.org/index.php/Manual:Ciphers(1)#CIPHER_STRINGS\fP
+\fI\%https://www.openssl.org/docs/man1.0.2/apps/ciphers.html#CIPHER\-STRINGS\fP
 .sp
 You can only set \fI\%opensslCipherConfig\fP during start\-up, and
 cannot change this setting using the \fBsetParameter\fP
 database command.
+.sp
+For version 4.2 and greater, the use of \fBTLS\fP options is preferred
+over \fBSSL\fP options. The TLS options have the same functionality as
+the \fBSSL\fP options.
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter opensslCipherConfig=\(aqHIGH:!EXPORT:!aNULL@STRENGTH\(aq \-\-tlsMode requireTLS \-\-tlsCertificateKeyFile Certs/server.pem
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+For versions 4.0 and earlier:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter opensslCipherConfig=\(aqHIGH:!EXPORT:!aNULL@STRENGTH\(aq \-\-sslMode requireSSL \-\-sslPEMKeyFile Certs/server.pem
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B opensslDiffieHellmanParameters
+New in version 3.6.
+
+.sp
+\fIAvailable on Linux only\fP
+.sp
+Specify the path to the PEM file that contains the OpenSSL
+Diffie\-Hellman parameters. Specifying the OpenSSL Diffie\-Hellman
+parameters enables support for dhe cipher suites during
+TLS/SSL encryption.
+.sp
+Ephemeral Diffie\-Hellman (DHE) cipher suites (and Ephemeral Elliptic
+Curve Diffie\-Hellman (ECDHE) cipher suites) provide
+tls\-forward\-secrecy\&. tls\-forward\-secrecy cipher suites
+create an ephemeral session key that is protected by the server\(aqs
+private key but never transmitted. This ensures that even if a
+server\(aqs private key is compromised, you cannot decrypt past
+sessions with the compromised key.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Starting in MongoDB 4.2, if
+\fI\%opensslDiffieHellmanParameters\fP is unset but
+ECDHE is enabled, MongoDB enables DHE using
+\fBffdhe3072\fP Diffie\-Hellman parameter, as defined in
+\fI\%RFC 7919#appendix\-A.2\fP\&. The \fBffdhe3072\fP is a strong parameter
+(i.e. size is greater than 1024). Strong parameters are not
+supported with Java 6 and 7 unless extended support has been
+purchased from Oracle.
+.UNINDENT
+.UNINDENT
+.sp
+You can only set \fI\%opensslDiffieHellmanParameters\fP during
+startup, and cannot change this setting using the
+\fBsetParameter\fP database command.
+.sp
+If for performance reasons, you need to disable support for DHE
+cipher suites, use the \fI\%opensslCipherConfig\fP parameter:
 .INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongod \-\-setParameter opensslCipherConfig=HIGH:!EXPORT:!aNULL@STRENGTH \-\-sslMode requireSSL \-\-sslPEMKeyFile Certs/server.pem
+mongod \-\-setParameter opensslCipherConfig=\(aqHIGH:!EXPORT:!aNULL:!DHE:!kDHE@STRENGTH\(aq ...
 .ft P
 .fi
 .UNINDENT
@@ -317,7 +513,7 @@ instance to use for proxy authentication.
 .B saslHostName
 Available for both \fBmongod\fP and \fBmongos\fP\&.
 .sp
-\fI\%saslHostName\fP overrides MongoDB’s default hostname
+\fI\%saslHostName\fP overrides MongoDB\(aqs default hostname
 detection for the purpose of configuring SASL and Kerberos
 authentication.
 .sp
@@ -507,6 +703,152 @@ db.adminCommand( { setParameter: 1, sslMode: "preferSSL" } )
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+\fBSEE ALSO:\fP
+.INDENT 7.0
+.INDENT 3.5
+\fI\%tlsMode\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B tlsMode
+New in version 4.2.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+Set to either:
+.INDENT 7.0
+.IP \(bu 2
+\fBpreferTLS\fP
+.IP \(bu 2
+\fBrequireTLS\fP
+.UNINDENT
+.sp
+The \fI\%tlsMode\fP parameter is useful during rolling
+upgrade to TLS/SSL to minimize
+downtime.
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, tlsMode: "preferTLS" } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
+.sp
+\fBSEE ALSO:\fP
+.INDENT 7.0
+.INDENT 3.5
+\fI\%sslMode\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B tlsWithholdClientCertificate
+\fIDefault\fP: false
+.sp
+New in version 4.2.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+A TLS certificate is set for a \fBmongod\fP or
+\fBmongos\fP either by the
+\fB\-\-tlsClusterFile\fP option or by the
+\fB\-\-tlsCertificateKeyFile\fP option when
+\fB\-\-tlsClusterFile\fP is not set. If the TLS
+certificate is set, by default, the instance sends the certificate when
+initiating intra\-cluster communications with other
+\fBmongod\fP or \fBmongos\fP instances in
+the deployment. Set \fBtlsWithholdClientCertificate\fP to \fB1\fP or \fBtrue\fP to
+direct the instance to withhold sending its TLS certificate during these
+communications. Use this option with
+\fB\-\-tlsAllowConnectionsWithoutCertificates\fP
+(to allow inbound connections without certificates) on all members of the
+deployment. \fBtlsWithholdClientCertificate\fP is mutually exclusive with
+\fB\-\-clusterAuthMode x509\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B tlsX509ClusterAuthDNOverride
+New in version 4.2.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+An alternative Distinguished Name (DN) that the instance can also
+use to identify members of the deployment.
+.sp
+For a MongoDB deployment that uses x.509 certificates for
+\fBclusterAuthMode\fP, deployment members identify
+each other using x.509 certificates (
+\fBnet.tls.clusterFile\fP, if specified, and
+\fBnet.tls.certificateKeyFile\fP) during intra\-cluster
+communications. For members of the same deployment, the \fBDN\fP from
+their certificates must have the same Organization attributes
+(\fBO\fP\(aqs), the Organizational Unit attributes (\fBOU\fP\(aqs), and the
+Domain Components (\fBDC\fP\(aqs).
+.sp
+If \fI\%tlsX509ClusterAuthDNOverride\fP is set for a member,
+the member can also use the override value when comparing the \fBDN\fP
+components (\fBO\fP\(aqs, \fBOU\fP\(aqs, and \fBDC\fP\(aqs) of the presented
+certificates. That is the member checks the presented certificates
+against its
+\fBnet.tls.clusterFile\fP/\fBnet.tls.certificateKeyFile\fP\&.
+If the DN does not match, the member checks the presented
+certifcate against the \fI\%tlsX509ClusterAuthDNOverride\fP
+value.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+If set, you must set this parameter on all members of the
+deployment.
+.UNINDENT
+.UNINDENT
+.sp
+You can use this parameter for a rolling update of certificates to
+new certificates that contain a new \fBDN\fP value. See
+/tutorial/rotate\-x509\-membership\-certificates\&.
+.sp
+For more information about membership certificate requirements, see
+x509\-member\-certificate\-requirements for details.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B sslWithholdClientCertificate
+\fIDefault\fP: false
+.sp
+Deprecated since version 4.2: Use \fI\%tlsWithholdClientCertificate\fP instead.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+A TLS certificate is set for a \fBmongod\fP or
+\fBmongos\fP either by the
+\fB\-\-tlsClusterFile\fP option or by the
+\fB\-\-tlsCertificateKeyFile\fP option when
+\fB\-\-tlsClusterFile\fP is not set. If the TLS
+certificate is set, by default, the instance sends the certificate when
+initiating intra\-cluster communications with other
+\fBmongod\fP or \fBmongos\fP instances in
+the deployment. Set \fBsslWithholdClientCertificate\fP to \fB1\fP or \fBtrue\fP to
+direct the instance to withhold sending its TLS certificate during these
+communications. Use this option with
+\fB\-\-tlsAllowConnectionsWithoutCertificates\fP
+(to allow inbound connections without certificates) on all members of the
+deployment. \fBsslWithholdClientCertificate\fP is mutually exclusive with
+\fB\-\-clusterAuthMode x509\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -556,6 +898,21 @@ MongoDB server still consume server resources, and this may adversely
 impact benign login attempts if the server is denying access to many
 other clients simultaneously.
 .UNINDENT
+.INDENT 0.0
+.TP
+.B allowRolesFromX509Certificates
+\fIDefault\fP: true
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+\fIAvailable starting in MongoDB 4.0.11 (and 3.6.14 and 3.4.22)\fP
+.sp
+A boolean flag that allows or disallows the retrieval of
+authorization roles from client x.509 certificates.
+.sp
+You can only set \fI\%allowRolesFromX509Certificates\fP during
+startup in the config file or on the command line.
+.UNINDENT
 .SS General Parameters
 .INDENT 0.0
 .TP
@@ -689,7 +1046,7 @@ pools. See \fI\%ShardingTaskExecutorPoolMaxSize\fP\&.
 .UNINDENT
 .sp
 \fBOnly\fP adjust this setting if your driver does \fInot\fP pool
-connections and you’re using authentication in the
+connections and you\(aqre using authentication in the
 context of a sharded cluster.
 .sp
 You can only set \fI\%connPoolMaxConnsPerHost\fP during startup
@@ -812,31 +1169,57 @@ db.adminCommand( { setParameter: 1, cursorTimeoutMillis: 300000 } )
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+Setting \fI\%cursorTimeoutMillis\fP to less than or equal
+to \fB0\fP results in all cursors being immediately eligible for timeout.
+Generally, the timeout value should be greater than the average amount of
+time for a query to return results. Use tools like the \fBcursor.explain()\fP
+cursor modifier to analyze the average query time and select an appropriate
+timeout period.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B failIndexKeyTooLong
-New in version 2.6.
-
-.sp
 Available for \fBmongod\fP only.
 .sp
-In MongoDB 2.6, if you attempt to insert or update a document so
-that the value of an indexed field is longer than the
-\fBIndex Key Length Limit\fP, the operation
-will fail and return an error to the client. In previous versions
-of MongoDB, these operations would successfully insert or modify a
-document but the index or indexes would not include references to
-the document.
+.INDENT 7.0
+Changed in version 4.2: .IP \(bu 2
+MongoDB removes the \fBIndex Key Limit\fP for
+featureCompatibilityVersion (fCV) set to
+\fB"4.2"\fP or greater.
+.IP \(bu 2
+In concert with the removal of the limit,
+\fBfailIndexTooLong\fP only applies for MongoDB 2.6
+through MongoDB versions with featureCompatibilityVersion (fCV) set to \fB"4.0"\fP or earlier.
+.UNINDENT
+
+.sp
+For MongoDB 2.6 through MongoDB versions with
+\fBfeatureCompatibilityVersion\fP (fCV) set to \fB"4.0"\fP or earlier,
+\fBIndex Key Length Limit\fP applies. If you
+attempt to insert or update a document whose index field exceeds
+the \fBIndex Key Length Limit\fP, the operation
+will fail and return an error to the client.
 .sp
 To avoid this issue, consider using hashed indexes or indexing a computed value. If you have an
 existing data set and want to disable this behavior so you can
 upgrade and then gradually resolve these indexing issues, you can
 use \fI\%failIndexKeyTooLong\fP to disable this behavior.
 .sp
-\fI\%failIndexKeyTooLong\fP defaults to \fBtrue\fP\&. When
-\fBfalse\fP, a 2.6 \fBmongod\fP instance will provide the 2.4
-behavior.
+\fBIMPORTANT:\fP
+.INDENT 7.0
+.INDENT 3.5
+Setting \fI\%failIndexKeyTooLong\fP to \fBfalse\fP is
+a temporary workaround, not a permanent solution to the
+problem of oversized index keys. With
+\fI\%failIndexKeyTooLong\fP set to \fBfalse\fP, queries can
+return incomplete results if they use indexes that skip over
+documents whose indexed fields exceed the
+\fBIndex Key Length Limit\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+\fI\%failIndexKeyTooLong\fP defaults to \fBtrue\fP\&.
 .sp
 Issue the following command to disable the index key length
 validation:
@@ -866,25 +1249,6 @@ mongod \-\-setParameter failIndexKeyTooLong=false
 .UNINDENT
 .INDENT 0.0
 .TP
-.B newCollectionsUsePowerOf2Sizes
-Deprecated since version 3.0.0: MongoDB deprecates the
-\fI\%newCollectionsUsePowerOf2Sizes\fP parameter such that
-you cannot set the \fI\%newCollectionsUsePowerOf2Sizes\fP to
-\fBfalse\fP and \fI\%newCollectionsUsePowerOf2Sizes\fP set to
-\fBtrue\fP is a no\-op. To disable the power of 2 allocation for a collection, use the
-\fBcollMod\fP command with the \fBnoPadding\fP flag
-or the \fBdb.createCollection()\fP method with the
-\fBnoPadding\fP option.
-
-.sp
-\fIDefault\fP: \fBtrue\fP\&.
-.sp
-Available for \fBmongod\fP only.
-.sp
-Available for the MMAPv1 storage engine only.
-.UNINDENT
-.INDENT 0.0
-.TP
 .B notablescan
 Available for \fBmongod\fP only.
 .sp
@@ -915,7 +1279,7 @@ the /tutorial/evaluate\-operation\-performance and
 sections and using the \fI\%logLevel\fP parameter,
 /reference/program/mongostat and profiling\&.
 .sp
-Don’t run production \fBmongod\fP instances with
+Don\(aqt run production \fBmongod\fP instances with
 \fI\%notablescan\fP because preventing collection scans can potentially
 affect queries in all databases, including administrative queries.
 .UNINDENT
@@ -958,7 +1322,7 @@ mongod \-\-setParameter ttlMonitorEnabled=false
 .INDENT 0.0
 .TP
 .B disableJavaScriptJIT
-Changed in version 4.0: The JavaScript engine’s JIT compiler is now disabled by default.
+Changed in version 4.0: The JavaScript engine\(aqs JIT compiler is now disabled by default.
 
 .sp
 Available for \fBmongod\fP only.
@@ -979,10 +1343,14 @@ db.adminCommand( { setParameter: 1, disableJavaScriptJIT: false } )
 .UNINDENT
 .UNINDENT
 .sp
-Be aware that \fBgroup\fP and \fB$where\fP will reuse existing
-JavaScript interpreter contexts, so changes to
-\fI\%disableJavaScriptJIT\fP may not take effect immediately for these
-operations.
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+\fB$where\fP will reuse existing JavaScript interpreter
+contexts, so changes to \fI\%disableJavaScriptJIT\fP may not
+take effect immediately for these operations.
+.UNINDENT
+.UNINDENT
 .sp
 Alternately, you may enable the JIT at startup time by starting the
 \fBmongod\fP instance with the following option:
@@ -1005,11 +1373,18 @@ New in version 3.4.
 .sp
 \fIDefault\fP: 500
 .sp
-Limits the amount of memory that simultaneous foreground index
+Limits the amount of memory that simultaneous index
 builds on one collection may consume for the duration of the
-builds.
+builds. The specified amount of memory is shared between all
+indexes built using a single
+\fBcreateIndexes\fP command or its shell helper
+\fBdb.collection.createIndexes()\fP\&.
 .sp
-Foreground index builds may be initiated either by a user command
+The memory consumed by an index build is separate from the
+WiredTiger cache memory (see
+\fBcacheSizeGB\fP).
+.sp
+Index builds may be initiated either by a user command
 such as Create Index
 or by an administrative process such as an
 initial sync\&.
@@ -1018,7 +1393,7 @@ Both are subject to the limit set by
 .sp
 An initial sync operation populates
 only one collection at a time and has no risk of exceeding the memory
-limit. However, it is possible for a user to start foreground index
+limit. However, it is possible for a user to start index
 builds on multiple collections in multiple databases simultaneously
 and potentially consume an amount of memory greater than the limit
 set in \fI\%maxIndexBuildMemoryUsageMegabytes\fP\&.
@@ -1032,13 +1407,52 @@ procedure as described on
 /tutorial/build\-indexes\-on\-replica\-sets\&.
 .UNINDENT
 .UNINDENT
+.sp
+Changed in version 4.2.
+
+.INDENT 7.0
+.IP \(bu 2
+For feature compatibility version (fcv) \fB"4.2"\fP,
+the index build memory limit applies to all index builds.
+.IP \(bu 2
+For feature compatibility version (fcv) \fB"4.0"\fP,
+the index build memory limit only applies to foreground
+index builds.
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
-.B watchdogPeriodSeconds
-New in version 3.6.
+.B reportOpWriteConcernCountersInServerStatus
+New in version 4.0.6.
 
 .sp
+\fIDefault\fP: false
+.sp
+A boolean flag that determines whether the
+\fBdb.serverStatus()\fP method and \fBserverStatus\fP
+command return \fBopWriteConcernCounters\fP information. [1]
+.sp
+You can only set
+\fI\%reportOpWriteConcernCountersInServerStatus\fP during
+startup in the config file or on the command line. For example:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter reportOpWriteConcernCountersInServerStatus=true
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP [1] 5
+Enabling \fI\%reportOpWriteConcernCountersInServerStatus\fP
+can have a negative performance impact; specificaly, when running
+\fIwithout\fP TLS.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B watchdogPeriodSeconds
 Available for \fBmongod\fP only.
 .sp
 \fIType\fP: integer
@@ -1048,30 +1462,62 @@ Available for \fBmongod\fP only.
 \fBNOTE:\fP
 .INDENT 7.0
 .INDENT 3.5
-Available only in MongoDB Enterprise. Not available on macOS.
+.INDENT 0.0
+.IP \(bu 2
+Starting in MongoDB 4.2, the Storage Node Watchdog is available in both the Community and
+MongoDB Enterprise editions.
+.IP \(bu 2
+In earlier versions (3.2.16+, 3.4.7+, 3.6.0+, 4.0.0+), the
+Storage Node Watchdog is only
+available in MongoDB Enterprise edition.
+.UNINDENT
+.UNINDENT
 .UNINDENT
+.sp
+Determines how frequent the Storage Node Watchdog checks the status of the monitored
+filesystems:
+.INDENT 7.0
+.IP \(bu 2
+The \fB\-\-dbpath\fP directory
+.IP \(bu 2
+The \fBjournal\fP directory inside the \fB\-\-dbpath\fP directory if
+\fBjournaling\fP is enabled
+.IP \(bu 2
+The directory of \fB\-\-logpath\fP file
+.IP \(bu 2
+The directory of \fB\-\-auditPath\fP file
 .UNINDENT
 .sp
-Determines how often the
-Storage Node Watchdog checks the status of
-the monitored filesystems.
+Valid values for \fI\%watchdogPeriodSeconds\fP are:
+.INDENT 7.0
+.IP \(bu 2
+\fB\-1\fP (the default), to disable/pause Storage Node Watchdog, or
+.IP \(bu 2
+An integer greater than or equal to 60.
+.UNINDENT
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
 .INDENT 3.5
-If a filesystem on a monitored directory becomes unresponsive, it can
-take a maximum of nearly \fItwice\fP the value of
-\fI\%watchdogPeriodSeconds\fP to terminate the \fBmongod\fP\&.
+.INDENT 0.0
+.IP \(bu 2
+If a filesystem on a monitored directory becomes unresponsive,
+it can take a maximum of nearly \fItwice\fP the value of
+\fI\%watchdogPeriodSeconds\fP to terminate the
+\fBmongod\fP\&.
+.IP \(bu 2
+If any of its monitored directory is a symlink to other
+volumes, the Storage Node Watchdog does not monitor the symlink
+target. For example, if the \fBmongod\fP uses
+\fBstorage.directoryPerDB: true\fP (or \fB\-\-directoryperdb\fP) and symlinks a database directory to
+another volume, the Storage Node Watchdog does not follow the
+symlink to monitor the target.
+.UNINDENT
 .UNINDENT
 .UNINDENT
 .sp
-Valid values are \-1, meaning the
-Storage Node Watchdog is disabled, or an
-integer greater than or equal to 60.
-.sp
-By default the Storage Node Watchdog is
-disabled. To enable it, \fI\%watchdogPeriodSeconds\fP must be set at
-startup time.
+To enable Storage Node Watchdog,
+\fI\%watchdogPeriodSeconds\fP must be set during startup.
 .INDENT 7.0
 .INDENT 3.5
 .sp
@@ -1083,15 +1529,16 @@ mongod \-\-setParameter watchdogPeriodSeconds=60
 .UNINDENT
 .UNINDENT
 .sp
-You can only enable the Storage Node Watchdog
-at startup.
+You can only enable the Storage Node Watchdog at startup. However, once enabled, you can
+pause the Storage Node Watchdog or
+change the \fI\%watchdogPeriodSeconds\fP during runtime.
 .sp
-However, once enabled, you can pause the Storage Node Watchdog or change the \fI\%watchdogPeriodSeconds\fP
-during runtime.
-.sp
-To pause the Storage Node Watchdog during
-runtime, set \fI\%watchdogPeriodSeconds\fP to \-1.
+Once enabled,
 .INDENT 7.0
+.IP \(bu 2
+To pause the Storage Node Watchdog
+during runtime, set \fI\%watchdogPeriodSeconds\fP to \-1.
+.INDENT 2.0
 .INDENT 3.5
 .sp
 .nf
@@ -1101,10 +1548,11 @@ db.adminCommand( { setParameter: 1, watchdogPeriodSeconds: \-1 } )
 .fi
 .UNINDENT
 .UNINDENT
-.sp
+.IP \(bu 2
 To resume or change the period during runtime, set
-\fI\%watchdogPeriodSeconds\fP to a number greater than or equal to 60.
-.INDENT 7.0
+\fI\%watchdogPeriodSeconds\fP to a number greater than or
+equal to 60.
+.INDENT 2.0
 .INDENT 3.5
 .sp
 .nf
@@ -1114,6 +1562,7 @@ db.adminCommand( { setParameter: 1, watchdogPeriodSeconds: 120 } )
 .fi
 .UNINDENT
 .UNINDENT
+.UNINDENT
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
@@ -1131,10 +1580,12 @@ startup time.
 Available for both \fBmongod\fP and \fBmongos\fP\&.
 .sp
 Specify an integer between \fB0\fP and \fB5\fP signifying the verbosity
-of the logging, where \fB5\fP is the most verbose.
+of the logging, where \fB5\fP is the
+most verbose. [2]
 .sp
-Consider the following example which sets the
-\fI\%logLevel\fP to \fB2\fP:
+The default \fI\%logLevel\fP is \fB0\fP (Informational).
+.sp
+The following example sets the \fI\%logLevel\fP to \fB2\fP:
 .INDENT 7.0
 .INDENT 3.5
 .sp
@@ -1146,14 +1597,22 @@ db.adminCommand( { setParameter: 1, logLevel: 2 } )
 .UNINDENT
 .UNINDENT
 .sp
-The default \fI\%logLevel\fP is \fB0\fP\&.
-.sp
 \fBSEE ALSO:\fP
 .INDENT 7.0
 .INDENT 3.5
-\fBverbosity\fP\&.
+.INDENT 0.0
+.IP \(bu 2
+\fI\%logComponentVerbosity\fP
+.IP \(bu 2
+\fBverbosity\fP
+.UNINDENT
 .UNINDENT
 .UNINDENT
+.IP [2] 5
+Starting in version 4.2, MongoDB includes the Debug verbosity level
+(1\-5) in the log messages\&. For example,
+if the verbosity level is 2, MongoDB logs \fBD2\fP\&. In previous
+versions, MongoDB log messages only specified \fBD\fP for Debug level.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1165,19 +1624,19 @@ Available for both \fBmongod\fP and \fBmongos\fP\&.
 .sp
 Sets the verbosity levels of various components for log messages\&. The verbosity level determines the
 amount of Informational and Debug
-messages MongoDB outputs.
+messages MongoDB outputs. [3]
 .sp
 The verbosity level can range from \fB0\fP to \fB5\fP:
 .INDENT 7.0
 .IP \(bu 2
-\fB0\fP is the MongoDB’s default log verbosity level, to include
+\fB0\fP is the MongoDB\(aqs default log verbosity level, to include
 Informational messages.
 .IP \(bu 2
 \fB1\fP to \fB5\fP increases the verbosity level to include
 Debug messages.
 .UNINDENT
 .sp
-For a component, you can also specify \fB\-1\fP to inherit the parent’s
+For a component, you can also specify \fB\-1\fP to inherit the parent\(aqs
 verbosity level.
 .sp
 To specify the verbosity level, use a document similar to the
@@ -1237,6 +1696,8 @@ The components correspond to the following settings:
 .IP \(bu 2
 \fBcontrol\fP
 .IP \(bu 2
+\fBftdc\fP
+.IP \(bu 2
 \fBgeo\fP
 .IP \(bu 2
 \fBindex\fP
@@ -1247,6 +1708,14 @@ The components correspond to the following settings:
 .IP \(bu 2
 \fBreplication\fP
 .IP \(bu 2
+\fBreplication.election\fP
+.IP \(bu 2
+\fBreplication.heartbeats\fP
+.IP \(bu 2
+\fBreplication.initialSync\fP
+.IP \(bu 2
+\fBreplication.rollback\fP
+.IP \(bu 2
 \fBrecovery\fP
 .IP \(bu 2
 \fBsharding\fP
@@ -1255,6 +1724,8 @@ The components correspond to the following settings:
 .IP \(bu 2
 \fBstorage.journal\fP
 .IP \(bu 2
+\fBtransaction\fP
+.IP \(bu 2
 \fBwrite\fP
 .UNINDENT
 .sp
@@ -1316,6 +1787,11 @@ mongod \-\-setParameter "logComponentVerbosity={command: 3}"
 The \fBmongo\fP shell also provides the \fBdb.setLogLevel()\fP
 to set the log level for a single component. For various ways to set
 the log verbosity level, see log\-messages\-configure\-verbosity\&.
+.IP [3] 5
+Starting in version 4.2, MongoDB includes the Debug verbosity level
+(1\-5) in the log messages\&. For example,
+if the verbosity level is 2, MongoDB logs \fBD2\fP\&. In previous
+versions, MongoDB log messages only specified \fBD\fP for Debug level.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1423,6 +1899,39 @@ db.adminCommand( { setParameter: 1, traceExceptions: true } )
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B suppressNoTLSPeerCertificateWarning
+New in version 4.0.1.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+\fIType\fP: boolean
+.sp
+\fIDefault\fP: false
+.sp
+By default, a \fBmongod\fP or \fBmongos\fP with
+TLS/SSL enabled and
+\fBnet.ssl.allowConnectionsWithoutCertificates\fP : \fBtrue\fP
+lets clients connect without providing a certificate for
+validation while logging an warning. Set
+\fBsuppressNoTLSPeerCertificateWarning\fP to \fB1\fP or \fBtrue\fP to
+suppress those warnings.
+.sp
+The following operation sets \fBsuppressNoTLSPeerCertificateWarning\fP
+to \fBtrue\fP:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, suppressNoTLSPeerCertificateWarning: true} )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS Diagnostic Parameters
 .sp
 To facilitate analysis of the MongoDB server behavior by MongoDB
@@ -1430,13 +1939,13 @@ engineers, MongoDB logs server statistics to diagnostic files at
 periodic intervals.
 .sp
 For \fBmongod\fP, the diagnostic data files are stored in the
-\fBdiagnostic.data\fP directory under the \fBmongod\fP instance’s
+\fBdiagnostic.data\fP directory under the \fBmongod\fP instance\(aqs
 \fB\-\-dbpath\fP or \fBstorage.dbPath\fP\&.
 .sp
 For \fBmongos\fP, the diagnostic data files, by default, are
-stored in a directory under the \fBmongos\fP instance’s
+stored in a directory under the \fBmongos\fP instance\(aqs
 \fB\-\-logpath\fP or \fBsystemLog.path\fP directory. The diagnostic
-data directory is computed by truncating the logpath’s file
+data directory is computed by truncating the logpath\(aqs file
 extension(s) and concatenating \fBdiagnostic.data\fP to the remaining
 name.
 .sp
@@ -1464,7 +1973,7 @@ for specific diagnostic purposes.
 New in version 3.2.
 
 .sp
-Changed in version 3.6: Available for both \fBmongod\fP and \fBmongos\fP\&.
+Changed in version 3.4.14: Available for both \fBmongod\fP and \fBmongos\fP\&.
 
 .sp
 \fIType\fP: boolean
@@ -1489,7 +1998,7 @@ mongod \-\-setParameter diagnosticDataCollectionEnabled=false
 .INDENT 0.0
 .TP
 .B diagnosticDataCollectionDirectoryPath
-New in version 3.6.
+New in version 3.4.14.
 
 .sp
 \fIType\fP: String
@@ -1501,7 +2010,7 @@ Specify the directory for the diagnostic directory for
 \fBmongos\fP creates the directory.
 .sp
 If unspecified, the diagnostic data directory is computed by
-truncating the \fBmongos\fP instance’s \fB\-\-logpath\fP or
+truncating the \fBmongos\fP instance\(aqs \fB\-\-logpath\fP or
 \fBsystemLog.path\fP file extension(s) and concatenating
 \fBdiagnostic.data\fP\&.
 .sp
@@ -1528,7 +2037,7 @@ New in version 3.2.
 Changed in version 3.4: Increased default size to 200 megabytes.
 
 .sp
-Changed in version 3.6: Available for both \fBmongod\fP and \fBmongos\fP\&.
+Changed in version 3.4.14: Available for both \fBmongod\fP and \fBmongos\fP\&.
 
 .sp
 \fIType\fP: integer
@@ -1565,7 +2074,7 @@ be greater than maximum diagnostic file size
 New in version 3.2.
 
 .sp
-Changed in version 3.6: Available for both \fBmongod\fP and \fBmongos\fP\&.
+Changed in version 3.4.14: Available for both \fBmongod\fP and \fBmongos\fP\&.
 
 .sp
 \fIType\fP: integer
@@ -1598,7 +2107,7 @@ The minimum value for
 New in version 3.2.
 
 .sp
-Changed in version 3.6: Available for both \fBmongod\fP and \fBmongos\fP\&.
+Changed in version 3.4.14: Available for both \fBmongod\fP and \fBmongos\fP\&.
 
 .sp
 \fIType\fP: integer
@@ -1628,31 +2137,36 @@ milliseconds.
 .SS Logical Session Parameters
 .INDENT 0.0
 .TP
-.B logicalSessionRefreshMinutes
-New in version 3.6.
-
+.B logicalSessionRefreshMillis
+.INDENT 7.0
+.INDENT 3.5
+.IP "Availability"
+.sp
+New in version 4.0.4 (and version 3.6.9).
+.UNINDENT
+.UNINDENT
 .sp
 Available for both \fBmongod\fP and \fBmongos\fP\&.
 .sp
 \fIType\fP: integer
 .sp
-\fIDefault\fP: 5
+\fIDefault\fP: 300000 (i.e. 5 minutes)
 .sp
-The interval (in minutes) at which the cache refreshes its logical
+The interval (in milliseconds) at which the cache refreshes its logical
 session records against the main session store.
 .sp
-You can only set \fI\%logicalSessionRefreshMinutes\fP at
+You can only set \fI\%logicalSessionRefreshMillis\fP at
 startup and cannot change this setting with the
 \fBsetParameter\fP command.
 .sp
-For example, to set the \fI\%logicalSessionRefreshMinutes\fP
+For example, to set the \fI\%logicalSessionRefreshMillis\fP
 for a \fBmongod\fP instance to 10 minutes:
 .INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongod \-\-setParameter logicalSessionRefreshMinutes=10
+mongod \-\-setParameter logicalSessionRefreshMillis=600000
 .ft P
 .fi
 .UNINDENT
@@ -1748,6 +2262,35 @@ mongod \-\-setParameter maxAcceptableLogicalClockDriftSecs=900
 .UNINDENT
 .INDENT 0.0
 .TP
+.B maxSessions
+New in version 4.0.1.
+
+.sp
+Available for both \fBmongod\fP and \fBmongos\fP\&.
+.sp
+\fIType\fP: integer
+.sp
+\fIDefault\fP: 1000000
+.sp
+The maximum number of sessions that can be cached.
+.sp
+You can only set \fI\%maxSessions\fP during start\-up.
+.sp
+For example, to set the \fI\%maxSessions\fP
+for a \fBmongod\fP instance to 1000:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter maxSessions=1000
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
 .B TransactionRecordMinimumLifetimeMinutes
 New in version 3.6.
 
@@ -1786,75 +2329,71 @@ mongod \-\-setParameter TransactionRecordMinimumLifetimeMinutes=20
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.SS Replication Parameters
 .INDENT 0.0
 .TP
-.B maxTransactionLockRequestTimeoutMillis
-New in version 4.0.
+.B enableFlowControl
+New in version 4.2.
 
 .sp
-Available for \fBmongod\fP only.
+\fIType\fP: boolean
 .sp
-\fIType\fP: integer
+\fIDefault\fP: true
 .sp
-\fIDefault\fP: 5
+Enables or disables the mechanism that controls the rate at which the
+primary applies its writes with the goal of keeping the secondary members\(aq
+\fBmajority committed\fP lag under a
+configurable maximum value.
 .sp
-The amount of time in milliseconds that multi\-document
-transactions should wait to aquire locks
-required by the operations in the transaction.
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+For flow control to engage, the replica set/sharded cluster must
+have: featureCompatibilityVersion (FCV) of
+\fB4.2\fP and read concern \fBmajority enabled\fP\&. That is, enabled flow
+control has no effect if FCV is not \fB4.2\fP or if read concern
+majority is disabled.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B flowControlTargetLagSeconds
+New in version 4.2.
+
 .sp
-If the transaction cannot aquire the locks after waiting
-\fI\%maxTransactionLockRequestTimeoutMillis\fP, the transaction
-aborts.
+\fIType\fP: integer
 .sp
-By default, multi\-document transactions
-wait \fB5\fP milliseconds. That is, if the transaction cannot acquire
-the locks within \fB5\fP milliseconds, the transaction aborts. If an
-operation provides a greater timeout in a lock request,
-\fI\%maxTransactionLockRequestTimeoutMillis\fP overrides the
-operation\-specific timeout.
+\fIDefault\fP: 10
 .sp
-You can set \fI\%maxTransactionLockRequestTimeoutMillis\fP to:
-.INDENT 7.0
-.IP \(bu 2
-\fB0\fP such that if the transaction cannot acquire the required
-locks immediately, the transaction aborts.
-.IP \(bu 2
-A number greater than \fB0\fP to wait the specified time to acquire
-the required locks. This can help obviate transaction aborts on
-momentary concurrent lock acquisitions, like fast\-running metadata
-operations. However, this could possibly delay the abort of
-deadlocked transaction operations.
-.IP \(bu 2
-\fB\-1\fP to use the operation specific timeout.
-.UNINDENT
+The target maximum \fBmajority committed\fP lag when running
+with flow control. When flow control is enabled, the mechanism
+attempts to keep the \fBmajority committed\fP lag under
+the specified seconds. The parameter has no effect if flow control
+is disabled.
 .sp
-The following sets the
-\fI\%maxTransactionLockRequestTimeoutMillis\fP to \fB20\fP
-milliseconds:
-.INDENT 7.0
-.INDENT 3.5
+The specified value must be greater than 0.
 .sp
-.nf
-.ft C
-db.adminCommand( { setParameter: 1, maxTransactionLockRequestTimeoutMillis: 20 } )
-.ft P
-.fi
-.UNINDENT
+In general, the default settings should suffice; however, if
+modifying from the default value, decreasing, rather than
+increasing, the value may prove to be more useful.
 .UNINDENT
+.INDENT 0.0
+.TP
+.B flowControlWarnThresholdSeconds
+New in version 4.2.
+
 .sp
-You can also set this parameter during start\-up:
-.INDENT 7.0
-.INDENT 3.5
+\fIType\fP: integer
 .sp
-.nf
-.ft C
-mongod \-\-setParameter maxTransactionLockRequestTimeoutMillis=20
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
+\fIDefault\fP: 10
+.sp
+The amount of time to wait to log a warning once the flow control
+mechanism detects the majority commit point has not moved.
+.sp
+The specified value must be greater than or equal to 0, with 0 to
+disable warnings.
 .UNINDENT
-.SS Replication Parameters
 .INDENT 0.0
 .TP
 .B oplogInitialFindMaxSeconds
@@ -1873,31 +2412,6 @@ data synchronization\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B replIndexPrefetch
-Available for \fBmongod\fP only.
-.sp
-Use \fI\%replIndexPrefetch\fP in conjunction with
-\fBreplSetName\fP when configuring a replica
-set. The default value is \fBall\fP and available
-options are:
-.INDENT 7.0
-.IP \(bu 2
-\fBnone\fP
-.IP \(bu 2
-\fBall\fP
-.IP \(bu 2
-\fB_id_only\fP
-.UNINDENT
-.sp
-By default secondary members of a replica set will
-load all indexes related to an operation into memory before
-applying operations from the oplog. You can modify this behavior so
-that the secondaries will only load the \fB_id\fP index. Specify
-\fB_id_only\fP or \fBnone\fP to prevent the \fBmongod\fP from
-loading \fIany\fP index into memory.
-.UNINDENT
-.INDENT 0.0
-.TP
 .B replWriterThreadCount
 New in version 3.2.
 
@@ -1916,23 +2430,30 @@ setting with the \fBsetParameter\fP command.
 .INDENT 0.0
 .TP
 .B rollbackTimeLimitSecs
-New in version 4.0.
-
-.sp
 \fIType\fP: 64\-bit integer
 .sp
-\fIDefault\fP: 1800
+\fIDefault\fP: 86400  (1 day)
 .sp
-Maximum age of data that will be rolled back in the event of a
-replication operations failure. If the time between the end of the
-rolled back instance oplog and the common point (the last point where
-the source node and the rolled back node had the same data) exceeds
-this value, the rollback will fail. Note that negative values for
+Maximum age of data that can be rolled back. Negative values for
 this parameter are not valid.
 .sp
-To set an effectively unlimited rollback period, set the value to
+Starting in MongoDB 4.2+ and 4.0.13+, if the time between the end
+of the to\-be\-rolledback instance\(aqs oplog and the first operation
+after the common point (the last point where the source node and the
+to\-be\-rolledback node had the same data) exceeds this value, the
+rollback will fail.
+.sp
+In MongoDB 4.0.0\-4.0.12, if the time between the end of the to\-be\-rolledback
+instance\(aqs oplog and the common point (the last point where the
+source node and the to\-be\-rolledback node had the same data) exceeds
+this value, the rollback will fail.
+.sp
+To effectively have an unlimited rollback period, set the value to
 \fB2147483647\fP which is the maximum value allowed and equivalent to
 roughly 68 years.
+.sp
+New in version 4.0.
+
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1954,7 +2475,7 @@ time, the secondary makes a no\-op write to advance the last applied
 time.
 .sp
 The following example sets the
-\fI\%waitForSecondaryBeforeNoopWriteMS\fP to 20 seconds:
+\fI\%waitForSecondaryBeforeNoopWriteMS\fP to 20 milliseconds:
 .INDENT 7.0
 .INDENT 3.5
 .sp
@@ -2025,36 +2546,86 @@ db.adminCommand( { setParameter: 1, createRollbackDataFiles: false } )
 .sp
 For more information, see rollback\-data\-files\&.
 .UNINDENT
-.SS Sharding Parameters
 .INDENT 0.0
 .TP
-.B AsyncRequestsSenderUseBaton
-Type: boolean
+.B enableElectionHandoff
+New in version 4.0.2.
+
 .sp
-Default: true
+\fIType\fP: boolean
 .sp
-A flag that enables performance optimization on Linux for
-scatter/gather operations on \fBmongos\fP when using a
-single \fI\%Task Executor connection pool\fP\&.
+\fIDefault\fP: true
 .sp
-\fBSEE ALSO:\fP
+A flag that can reduce the downtime after the primary steps down
+from either the \fBrs.stepDown()\fP method or the
+\fBreplSetStepDown\fP command. Specifically, if true, when a
+primary steps down after \fBrs.stepDown()\fP (or the
+\fBreplSetStepDown\fP command without the \fBforce: true\fP),
+it nominates an eligible secondary to call an election immediately.
+If false, after the step down, secondaries can wait up to
+\fBsettings.electionTimeoutMillis\fP before calling an election.
+.sp
+An eligible secondary must be caught up with the stepped down
+primary and have \fBpriority\fP greater than 0. If
+multiple secondary members meet this criteria, the stepped down
+primary selects the eligible secondary with the highest
+\fBpriority\fP\&. If the more than one eligible
+secondary members have the same \fBpriority\fP, the
+stepped down primary selects the secondary with the lowest
+\fB_id\fP\&. The stepped down primary does not wait
+for the effects of the handoff.
+.sp
+The parameter has no impact if the primary steps down for reasons
+other than \fBrs.stepDown()\fP (or the
+\fBreplSetStepDown\fP command without the \fBforce: true\fP).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B replBatchLimitBytes
+\fIDefault\fP: 104857600 (100MB)
+.sp
+Sets the maximum oplog application batch size in bytes.
+.sp
+Values can range from 16777216 (16MB) to 104857600 (100MB) inclusive.
+.sp
+The following example sets \fI\%replBatchLimitBytes\fP
+to 64 MB so that the rollback files are not created:
 .INDENT 7.0
 .INDENT 3.5
-\fI\%taskExecutorPoolSize\fP
+.sp
+.nf
+.ft C
+mongod \-\-setParameter replBatchLimitBytes=67108864
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
 .sp
-New in version 4.0.
+During runtime, you can also set the parameter with the
+\fBsetParameter\fP command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, replBatchLimitBytes: 64 * 1024 * 1024 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+New in version 4.0.10.
 
 .UNINDENT
-.INDENT 0.0
-.TP
-.B recoverShardingState
-Available for \fBmongod\fP only.
+.SS Sharding Parameters
 .sp
-Specify a boolean to check or ignore sharding state recovery
-information. Default is \fBtrue\fP to check the sharding state
-recovery information.
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Starting in version 4.2, MongoDB removes the parameter
+\fBAsyncRequestsSenderUseBaton\fP and always enables the performance
+enhancement controlled by the parameter.
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -2078,7 +2649,8 @@ replica set is the config server replica set:
 .IP \(bu 2
 For MongoDB 3.2.0\-3.2.9, the monitoring \fBmongod\fP or
 \fBmongos\fP instance will become unusable and needs to be
-restarted. See the troubleshooting guide for more details.
+restarted. See the \fI\%v3.2 troubleshooting guide\fP
+for more details.
 .IP \(bu 2
 For MongoDB 3.2.10 and later 3.2\-series, see also
 \fI\%timeOutMonitoringReplicaSets\fP\&.
@@ -2103,7 +2675,8 @@ If the monitored replica set is the config server replica set and
 must restart \fBmongod\fP or \fBmongos\fP if the
 \fBmongod\fP or \fBmongos\fP instance cannot reach any of
 the config servers for the specified number of times. See the
-troubleshooting guide for more details.
+\fI\%v3.2 troubleshooting guide\fP
+for more details.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -2122,7 +2695,7 @@ this setting using the \fBsetParameter\fP database command.
 .sp
 If set, \fI\%ShardingTaskExecutorPoolHostTimeoutMS\fP should be
 greater than the sum of
-:parameter\(gaShardingTaskExecutorPoolRefreshRequirementMS\(ga and
+\fI\%ShardingTaskExecutorPoolRefreshRequirementMS\fP and
 \fI\%ShardingTaskExecutorPoolRefreshTimeoutMS\fP\&. Otherwise,
 \fBmongos\fP adjusts the value of
 \fI\%ShardingTaskExecutorPoolHostTimeoutMS\fP to be greater than the
@@ -2238,7 +2811,7 @@ pool can open to any given \fBmongod\fP instance.
 first time a connection to a new host is requested from the pool.
 While the pool is idle, the pool maintains this number of
 connections until \fI\%ShardingTaskExecutorPoolHostTimeoutMS\fP
-milliseconds pass without the any application using that pool.
+milliseconds pass without any application using that pool.
 .sp
 You can only set this parameter during start\-up and cannot change
 this setting using the \fBsetParameter\fP database command.
@@ -2328,6 +2901,103 @@ mongos \-\-setParameter ShardingTaskExecutorPoolRefreshTimeoutMS=30000
 .UNINDENT
 .INDENT 0.0
 .TP
+.B ShardingTaskExecutorPoolReplicaSetMatching
+New in version 4.2.
+
+.sp
+Type: string
+.sp
+Default: "matchPrimaryNode"
+.sp
+Available for \fBmongos\fP only.
+.sp
+The policy that determines the minimum size limit of the
+\fBmongos\fP instance\(aqs connection pools to the sharded
+cluster\(aqs replica set secondaries.
+.sp
+Available values are:
+.TS
+center;
+|l|l|.
+_
+T{
+Matching Policy
+T}	T{
+Description
+T}
+_
+T{
+\fB"matchPrimaryNode"\fP (Default)
+T}	T{
+For each replica set in the sharded cluster (i.e. shard
+replica set and config servers), the minimum size limit of
+the \fBmongos\fP instance\(aqs connection pool to each
+secondary of that replica set is equal to the size of its
+connection pool to the primary.
+.sp
+In case of primary stepdown, \fBmatchPrimaryNode\fP ensures
+that any secondary that becomes the primary can handle the
+current level of primary reads and writes.
+T}
+_
+T{
+\fB"matchBusiestNode"\fP
+T}	T{
+For each replica set in the sharded cluster (i.e. shard
+replica set and config servers), the minimum size limit of
+the \fBmongos\fP instance\(aqs connection pool to each
+member of that replica set is equal to the largest among
+the active connections counts to the primary and each
+secondary members.
+.sp
+With \fB"matchBusiestNode"\fP, \fBmongos\fP maintains
+enough connections to each secondary to handle the current
+level of primary and secondary reads and writes. The number
+of connections to maintain in the pool decreases as the
+number of active connections decreases.
+T}
+_
+T{
+\fB"disabled"\fP
+T}	T{
+For each replica set in the sharded cluster (i.e. shard
+replica set and config servers), the minimum number of
+connections in the \fBmongos\fP instance\(aqs
+connection pool to each secondary is equal to the
+\fI\%ShardingTaskExecutorPoolMinSize\fP\&.
+T}
+_
+.TE
+.sp
+The following example sets the
+\fI\%ShardingTaskExecutorPoolReplicaSetMatching\fP to
+\fB"matchBusiestNode"\fP during startup:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter ShardingTaskExecutorPoolReplicaSetMatching="matchBusiestNode"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+During runtime, you can also set the parameter with the
+\fBsetParameter\fP command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1,  ShardingTaskExecutorPoolReplicaSetMatching: "matchBusiestNode" } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
 .B taskExecutorPoolSize
 Changed in version 4.0.
 
@@ -2354,9 +3024,18 @@ Executor connection pools is 64.
 .UNINDENT
 .sp
 Starting in MongoDB 4.0, the default value of
-\fI\%taskExecutorPoolSize\fP is \fB1\fP\&. For the previous
-behavior, set \fI\%taskExecutorPoolSize\fP to 0 and, on Linux,
-set \fI\%AsyncRequestsSenderUseBaton\fP to \fBfalse\fP\&.
+\fI\%taskExecutorPoolSize\fP is \fB1\fP:
+.INDENT 7.0
+.IP \(bu 2
+In MongoDB 4.0 deployment, you can set
+\fI\%taskExecutorPoolSize\fP to \fB0\fP and, on Linux, set
+\fI\%AsyncRequestsSenderUseBaton\fP to
+\fBfalse\fP for the previous behavior.
+.IP \(bu 2
+In MongoDB 4.2+ deployment, MongoDB removes the
+\fBAsyncRequestsSenderUseBaton\fP parameter and always enables the
+performance enhancement controlled by the parameter.
+.UNINDENT
 .sp
 You can only set this parameter during start\-up and cannot change
 this setting using the \fBsetParameter\fP database command.
@@ -2385,6 +3064,95 @@ mongos \-\-setParameter taskExecutorPoolSize=6
 .UNINDENT
 .INDENT 0.0
 .TP
+.B migrateCloneInsertionBatchDelayMS
+New in version 4.0.5: The parameter is also available starting in 3.4.18 and 3.6.10
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+Type: Non\-negative integer
+.sp
+Default: 0
+.sp
+Time in milliseconds to wait between batches of insertions during
+cloning step of the migration process. This wait is in addition to
+the \fBsecondaryThrottle\fP\&.
+.sp
+The default value of \fB0\fP indicates no additional wait.
+.sp
+The following sets the \fI\%migrateCloneInsertionBatchDelayMS\fP to 200
+milliseconds:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter migrateCloneInsertionBatchDelayMS=200
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The parameter may also be set using the \fBsetParameter\fP
+command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, migrateCloneInsertionBatchDelayMS: 200 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B migrateCloneInsertionBatchSize
+New in version 4.0.5: The parameter is also available starting in 3.4.18 and 3.6.10
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+Type: Non\-negative integer
+.sp
+Default: 0
+.sp
+The maximum number of documents to insert in a single batch during
+the cloning step of the migration process.
+.sp
+The default value of \fB0\fP indicates no maximum number of documents
+per batch. However, in practice, this results in batches that
+contain up to 16 MB of documents.
+.sp
+The following sets the \fI\%migrateCloneInsertionBatchSize\fP to 100
+documents:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter migrateCloneInsertionBatchSize=100
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The parameter may also be set using the \fBsetParameter\fP
+command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, migrateCloneInsertionBatchSize: 100 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
 .B orphanCleanupDelaySecs
 New in version 3.6.
 
@@ -2443,6 +3211,146 @@ db.adminCommand( { setParameter: 1, orphanCleanupDelaySecs: 1200 } )
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B rangeDeleterBatchDelayMS
+New in version 4.0.1: The parameter is also available starting in 3.4.17 and 3.6.7.
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+Type: Non\-negative integer
+.sp
+Default: 20
+.sp
+The amount of time in milliseconds to wait before the next batch of
+deletion during the cleanup stage of chunk migration (or the \fBcleanupOrphaned\fP
+command).
+.sp
+In MongoDB 3.4, consider whether _secondaryThrottle is set before modifying the
+\fI\%rangeDeleterBatchDelayMS\fP\&. In MongoDB 3.4, the
+_secondaryThrottle replication delay occurs after each document deletion
+instead of after the batch deletion.
+.sp
+In MongoDB 3.6+, the _secondaryThrottle replication delay occurs after each batch deletion.
+.sp
+The following sets the \fI\%rangeDeleterBatchDelayMS\fP to 200
+milliseconds:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter rangeDeleterBatchDelayMS=200
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The parameter may also be set using the \fBsetParameter\fP
+command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, rangeDeleterBatchDelayMS: 200 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B rangeDeleterBatchSize
+New in version 4.0.5: The parameter is also available starting in 3.4.19 and 3.6.10
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+Type: Non\-negative integer
+.sp
+Default: 0
+.sp
+The maximum number of documents in each batch to delete during the
+cleanup stage of chunk migration
+(or the \fBcleanupOrphaned\fP command).
+.sp
+The default value of \fB0\fP indicates that the system chooses an
+appropriate value, generally 128 documents.
+.sp
+The following sets the \fI\%rangeDeleterBatchSize\fP to 100
+documents:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter rangeDeleterBatchSize=100
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The parameter may also be set using the \fBsetParameter\fP
+command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, rangeDeleterBatchSize: 100 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B skipShardingConfigurationChecks
+New in version 3.6.3.
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+Type: boolean
+.sp
+Default: false
+.sp
+When \fBtrue\fP, allows for starting a shard member or config server
+member as a standalone for maintenance operations. This parameter is
+mutually exclusive with the \fB\-\-configsvr\fP or \fB\-\-shardsvr\fP options.
+.sp
+You can only set this parameter during start\-up and cannot change
+this setting using the \fBsetParameter\fP database command.
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter skipShardingConfigurationChecks=true
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBIMPORTANT:\fP
+.INDENT 7.0
+.INDENT 3.5
+Once maintenance has completed, remove the
+\fI\%skipShardingConfigurationChecks\fP parameter when
+restarting the \fBmongod\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+The parameter is also available for MongoDB versions:
+.INDENT 7.0
+.IP \(bu 2
+MongoDB 3.2.19+
+.IP \(bu 2
+MongoDB 3.4.11+
+.UNINDENT
+.UNINDENT
 .SS Storage Parameters
 .INDENT 0.0
 .TP
@@ -2514,7 +3422,7 @@ New in version 3.6.
 .sp
 If \fI\%honorSystemUmask\fP is set to \fBtrue\fP, new files
 created by MongoDB have permissions in accordance with the
-user’s \fBumask\fP settings.
+user\(aqs \fBumask\fP settings.
 .sp
 If \fI\%honorSystemUmask\fP is set to \fBfalse\fP, new files
 created by MongoDB have permissions set to \fB600\fP, which gives
@@ -2544,6 +3452,64 @@ mongod \-\-setParameter honorSystemUmask=true
 .SS WiredTiger Parameters
 .INDENT 0.0
 .TP
+.B wiredTigerMaxCacheOverflowSizeGB
+\fIAvailable starting in MongoDB 4.2.1 (and 4.0.12)\fP
+.sp
+\fIDefault\fP: 0 (No specified maximum)
+.sp
+Available for \fBmongod\fP only.
+.sp
+Specify the maximum size (in GB) for the "lookaside (or cache
+overflow) table" file \fBWiredTigerLAS.wt\fP\&.
+.sp
+The parameter can accept the following values:
+.TS
+center;
+|l|l|.
+_
+T{
+Value
+T}	T{
+Description
+T}
+_
+T{
+\fB0\fP
+T}	T{
+The default value. If set to \fB0\fP, the file size is
+unbounded.
+T}
+_
+T{
+number >= 0.1
+T}	T{
+The maximum size (in GB). If the \fBWiredTigerLAS.wt\fP
+file exceeds this size, \fBmongod\fP exits with a
+fatal assertion. You can clear the \fBWiredTigerLAS.wt\fP
+file and restart \fBmongod\fP\&.
+T}
+_
+.TE
+.sp
+You can only set this parameter during runtime using the
+\fBsetParameter\fP database command:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, wiredTigerMaxCacheOverflowSizeGB: 100 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+To set the maximum size during start up, use the
+\fBstorage.wiredTiger.engineConfig.maxCacheOverflowFileSizeGB\fP
+instead.
+.UNINDENT
+.INDENT 0.0
+.TP
 .B wiredTigerConcurrentReadTransactions
 New in version 3.0.0.
 
@@ -2654,7 +3620,8 @@ New in version 2.6.5.
 \fBNOTE:\fP
 .INDENT 7.0
 .INDENT 3.5
-Available only in \fI\%MongoDB Enterprise\fP\&.
+Available only in \fI\%MongoDB Enterprise\fP
+and \fI\%MongoDB Atlas\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -2698,6 +3665,8 @@ more than logging only the authorization failures.
 New in version 4.0.
 
 .sp
+Available for \fBmongod\fP only.
+.sp
 \fIDefault\fP: 60
 .sp
 Specifies the lifetime of multi\-document transactions\&. Transactions that exceeds this limit are
@@ -2706,8 +3675,14 @@ process. The cleanup process runs every
 \fI\%transactionLifetimeLimitSeconds\fP/2 seconds or at least
 once per every 60 seconds.
 .sp
+The cleanup process helps relieve storage cache pressure.
+.sp
 The minimum value for transactionLifetimeLimitSeconds is \fB1\fP
 second.
+.sp
+The following sets the
+\fI\%transactionLifetimeLimitSeconds\fP to \fB30\fP
+seconds:
 .INDENT 7.0
 .INDENT 3.5
 .sp
@@ -2731,10 +3706,81 @@ mongod \-\-setParameter "transactionLifetimeLimitSeconds=30"
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+To set the parameter for a sharded cluster, the parameter must be
+modified for all shard replica set members.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B maxTransactionLockRequestTimeoutMillis
+New in version 4.0.
+
+.sp
+Available for \fBmongod\fP only.
+.sp
+\fIType\fP: integer
+.sp
+\fIDefault\fP: 5
+.sp
+The maximum amount of time in milliseconds that multi\-document
+transactions should wait to acquire locks
+required by the operations in the transaction.
+.sp
+If the transaction cannot acquire the locks after waiting
+\fI\%maxTransactionLockRequestTimeoutMillis\fP, the transaction
+aborts.
+.sp
+By default, multi\-document transactions
+wait \fB5\fP milliseconds. That is, if the transaction cannot acquire
+the locks within \fB5\fP milliseconds, the transaction aborts. If an
+operation provides a greater timeout in a lock request,
+\fI\%maxTransactionLockRequestTimeoutMillis\fP overrides the
+operation\-specific timeout.
+.sp
+You can set \fI\%maxTransactionLockRequestTimeoutMillis\fP to:
+.INDENT 7.0
+.IP \(bu 2
+\fB0\fP such that if the transaction cannot acquire the required
+locks immediately, the transaction aborts.
+.IP \(bu 2
+A number greater than \fB0\fP to wait the specified time to acquire
+the required locks. This can help obviate transaction aborts on
+momentary concurrent lock acquisitions, like fast\-running metadata
+operations. However, this could possibly delay the abort of
+deadlocked transaction operations.
+.IP \(bu 2
+\fB\-1\fP to use the operation specific timeout.
+.UNINDENT
+.sp
+The following sets the
+\fI\%maxTransactionLockRequestTimeoutMillis\fP to \fB20\fP
+milliseconds:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+db.adminCommand( { setParameter: 1, maxTransactionLockRequestTimeoutMillis: 20 } )
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You can also set this parameter during start\-up:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongod \-\-setParameter maxTransactionLockRequestTimeoutMillis=20
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .SH AUTHOR
 MongoDB Documentation Project
 .SH COPYRIGHT
-2008-2018
+2008-2019
 .\" Generated by docutils manpage writer.
 .
diff --git a/debian/mongodump.1 b/debian/mongodump.1
index 317550be310..dfb163851aa 100644
--- a/debian/mongodump.1
+++ b/debian/mongodump.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGODUMP" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGODUMP" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongodump \- MongoDB Data Dump Utility
 .
@@ -35,6 +35,10 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
+\fI\%Usage in Backup Strategy\fP
+.IP \(bu 2
 \fI\%Syntax\fP
 .IP \(bu 2
 \fI\%Behavior\fP
@@ -55,16 +59,41 @@ of  mongodump\&.
 .UNINDENT
 .SH SYNOPSIS
 .sp
-\fI\%mongodump\fP is a utility for creating a binary export of the
-contents of a database. \fI\%mongodump\fP can export data from
-either \fBmongod\fP or \fBmongos\fP instances.
+\fI\%mongodump\fP is a utility for creating a binary export of
+the contents of a database. \fI\%mongodump\fP can export data
+from either \fBmongod\fP or \fBmongos\fP instances;
+i.e. can export data from standalone, replica set, and sharded cluster
+deployments.
+.SH AVAILABILITY
+.sp
+The \fI\%mongodump\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
+.SH USAGE IN BACKUP STRATEGY
+.SS Standalones/Replica Sets
 .sp
-\fI\%mongodump\fP can be a part of a backup strategy with \fBmongorestore\fP for partial
-backups based on a query, syncing from production to staging or
-development environments, or changing the storage engine of a
-standalone. However, the use of \fI\%mongodump\fP and
-\fBmongorestore\fP as a backup strategy can be problematic for
-sharded clusters and replica sets.
+For standalone or a replica set, \fI\%mongodump\fP can be a part
+of a backup strategy with
+\fBmongorestore\fP for partial backups based on a query,
+syncing from production to staging or development environments, or
+changing the storage engine of a standalone.
 .sp
 For an overview of \fI\%mongodump\fP in conjunction with
 \fBmongorestore\fP part of a backup and recovery strategy, see:
@@ -72,10 +101,26 @@ For an overview of \fI\%mongodump\fP in conjunction with
 .IP \(bu 2
 /tutorial/backup\-and\-restore\-tools
 .IP \(bu 2
-/tutorial/backup\-sharded\-cluster\-with\-database\-dumps
-.IP \(bu 2
 /core/backups
 .UNINDENT
+.SS Sharded Cluster
+.sp
+\fI\%mongodump\fP and \fBmongorestore\fP
+\fBcannot\fP be part of a backup strategy for 4.2+ sharded clusters
+that have sharded transactions in progress as these tools cannot
+guarantee a atomicity guarantees of data across the shards.
+.sp
+For 4.2+ sharded clusters with in\-progress sharded transactions, for
+coordinated backup and restore processes that maintain the atomicity
+guarantees of transactions across shards, see:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%MongoDB Atlas\fP,
+.IP \(bu 2
+\fI\%MongoDB Cloud Manager\fP, or
+.IP \(bu 2
+\fI\%MongoDB Ops Manager\fP\&.
+.UNINDENT
 .SH SYNTAX
 .sp
 Run \fI\%mongodump\fP from the system command line, not the \fBmongo\fP shell.
@@ -114,7 +159,7 @@ Specify the hostname and port in the \fI\%\-\-uri connection string\fP:
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongodb0.example.com:27017" [additional options]
+mongodump \-\-uri="mongodb://mongodb0.example.com:27017" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -126,7 +171,7 @@ Specify the hostname and port in the \fI\%\-\-host\fP:
 .sp
 .nf
 .ft C
-mongodump \-\-host "mongodb0.example.com:27017"  [additional options]
+mongodump \-\-host="mongodb0.example.com:27017"  [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -138,7 +183,7 @@ Specify the hostname and port in the \fI\%\-\-host\fP and \fI\%\-\-port\fP:
 .sp
 .nf
 .ft C
-mongodump \-\-host "mongodb0.example.com" \-\-port 27017 [additional options]
+mongodump \-\-host="mongodb0.example.com" \-\-port=27017 [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -157,7 +202,7 @@ Specify the replica set name and members in the \fI\%\-\-uri connection string\f
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName" [additional options]
+mongodump \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -169,7 +214,7 @@ Specify the replica set name and members in the \fI\%\-\-host\fP:
 .sp
 .nf
 .ft C
-mongodump \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com" [additional options]
+mongodump \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -188,7 +233,7 @@ You can specify the read preference in the
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName&readPreference=secondary" [additional options]
+mongodump \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName&readPreference=secondary" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -201,7 +246,7 @@ If specifying the read preference tags, include the
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName&readPreference=secondary&readPreferenceTags=region:east" [additional options]
+mongodump \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=myReplicaSetName&readPreference=secondary&readPreferenceTags=region:east" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -215,7 +260,7 @@ option. The command\-line option takes a string if specifying only the read pref
 .sp
 .nf
 .ft C
-mongodump \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference secondary [additional options]
+mongodump \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference=secondary [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -231,7 +276,7 @@ maxStalenessSeconds:
 .sp
 .nf
 .ft C
-mongodump \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq [additional options]
+mongodump \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -251,7 +296,7 @@ Specify the hostname of the \fBmongos\fP instance in the
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongos0.example.com:27017" [additional options]
+mongodump \-\-uri="mongodb://mongos0.example.com:27017" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -263,7 +308,7 @@ Specify the hostname and port of the \fBmongos\fP instance in the \fI\%\-\-host\
 .sp
 .nf
 .ft C
-mongodump \-\-host "mongos0.example.com:27017" [additional options]
+mongodump \-\-host="mongos0.example.com:27017" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -282,7 +327,7 @@ You can specify the read preference in the
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongos0.example.com:27017/?readPreference=secondary" [additional options]
+mongodump \-\-uri="mongodb://mongos0.example.com:27017/?readPreference=secondary" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -295,7 +340,7 @@ If specifying the read preference tags, include the
 .sp
 .nf
 .ft C
-mongodump \-\-uri "mongodb://mongos0.example.com:27017/?readPreference=secondary&readPreferenceTags=region:east" [additional options]
+mongodump \-\-uri="mongodb://mongos0.example.com:27017/?readPreference=secondary&readPreferenceTags=region:east" [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -309,7 +354,7 @@ option.  The command\-line option takes a string if specifying only the read pre
 .sp
 .nf
 .ft C
-mongodump \-\-host "mongos0.example.com:27017" \-\-readPreference secondary [additional options]
+mongodump \-\-host="mongos0.example.com:27017" \-\-readPreference=secondary [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -325,7 +370,7 @@ maxStalenessSeconds:
 .sp
 .nf
 .ft C
-mongodump \-\-host "mongos0.example.com:27017" \-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq [additional options]
+mongodump \-\-host="mongos0.example.com:27017" \-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -370,6 +415,23 @@ read\-only views\&. By default,
 create a binary export of the documents included in the view. To
 capture the documents in a view use \fI\%\-\-viewsAsCollections\fP\&.
 
+.SS Metadata Format
+.sp
+Starting in version 4.2, \fI\%mongodump\fP uses Extended
+JSON v2.0 (Canonical) format
+for the metadata files. To parse these files for restore, use
+\fBmongorestore\fP version 4.2+ that supports Extended
+JSON v2.0 (Canonical or Relaxed mode) format.
+.INDENT 0.0
+.INDENT 3.5
+.SS Tip
+.sp
+If general, use corresponding versions of \fI\%mongodump\fP
+and \fBmongorestore\fP\&. That is, to restore data files
+created with a specific version of \fI\%mongodump\fP, use the
+corresponding version of \fBmongorestore\fP\&.
+.UNINDENT
+.UNINDENT
 .SS Overwrite Files
 .sp
 \fI\%mongodump\fP overwrites output files if they exist in the
@@ -456,7 +518,7 @@ Returns the \fBmongodump\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -467,7 +529,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -515,7 +577,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>, \-h <hostname><:port>
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
 \fIDefault\fP: localhost:27017
 .sp
 Specifies a resolvable hostname for the \fBmongod\fP to which to
@@ -530,7 +592,7 @@ the following:
 .sp
 .nf
 .ft C
-\-\-host <replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
+\-\-host=<replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
@@ -546,7 +608,7 @@ the host and port of only that member:
 .sp
 .nf
 .ft C
-\-\-host <hostname1><:port>
+\-\-host=<hostname1><:port>
 .ft P
 .fi
 .UNINDENT
@@ -566,7 +628,7 @@ You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -604,7 +666,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -645,7 +707,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -664,7 +726,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
@@ -683,7 +745,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -715,8 +777,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -759,7 +819,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
+.B \-\-username=<username>, \-u=<username>
 Specifies a username with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -773,7 +833,7 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
+.B \-\-password=<password>, \-p=<password>
 Specifies a password with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -793,7 +853,7 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
+.B \-\-authenticationDatabase=<dbname>
 Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
 See user\-authentication\-database\&.
 .sp
@@ -813,7 +873,7 @@ credentials.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongodump\fP instance uses to
@@ -910,7 +970,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-db <database>, \-d <database>
+.B \-\-db=<database>, \-d=<database>
 Specifies a database to backup. If you do not specify a database,
 \fI\%mongodump\fP copies all databases in this instance into the dump
 files.
@@ -924,23 +984,40 @@ You cannot specify both \fI\%\-\-db\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-collection <collection>, \-c <collection>
+.B \-\-collection=<collection>, \-c=<collection>
 Specifies a collection to backup. If you do not specify a collection,
 this option copies all collections in the specified database or instance
 to the dump files.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-query <json>, \-q <json>
-Provides a JSON document as a query that optionally limits the
-documents included in the output of \fI\%mongodump\fP\&.
+.B \-\-query=<json>, \-q=<json>
+Provides a JSON document as a query that optionally limits
+the documents included in the output of \fI\%mongodump\fP\&. To
+use the \fB\-\-query\fP option, you must also specify the
+\fI\%\-\-collection\fP option.
 .sp
 You must enclose the query document in single quotes (\fB\(aq{ ... }\(aq\fP) to ensure that it does
 not interact with your shell environment.
+.sp
+Starting in MongoDB 4.2, the query \fBmust\fP be in
+Extended JSON v2 format (either relaxed or canonical/strict
+mode), including enclosing the
+field names and operators in quotes.  For example:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongodump \-d=test \-c=records \-q=\(aq{ "a": { "$gte": 3 }, "date": { "$lt": { "$date": "2016\-01\-01T00:00:00.000Z" } } }\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-queryFile <path>
+.B \-\-queryFile=<path>
 New in version 3.2.
 
 .sp
@@ -951,7 +1028,7 @@ are too large to fit in your terminal\(aqs buffer.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-readPreference <string|document>
+.B \-\-readPreference=<string|document>
 \fIDefault\fP: \fBprimary\fP
 .sp
 Specifies the read preference for
@@ -964,7 +1041,7 @@ A string if specifying only the read preference mode:
 .sp
 .nf
 .ft C
-\-\-readPreference secondary
+\-\-readPreference=secondary
 .ft P
 .fi
 .UNINDENT
@@ -978,7 +1055,7 @@ optional maxStalenessSeconds:
 .sp
 .nf
 .ft C
-\-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
+\-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
 .ft P
 .fi
 .UNINDENT
@@ -1036,7 +1113,7 @@ output to the stream.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-out <path>, \-o <path>
+.B \-\-out=<path>, \-o=<path>
 Specifies the directory where \fI\%mongodump\fP will write
 BSON files for the dumped databases. By default,
 \fI\%mongodump\fP saves output files in a directory named
@@ -1054,22 +1131,45 @@ You cannot use the \fB\-\-archive\fP option with the
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-archive <file or null>
+.B \-\-archive=<file>
 New in version 3.2.
 
 .sp
-Writes the output to a single archive file or to the standard output
-(\fBstdout\fP).
+Writes the output to a specified archive file or, if the archive
+file is unspecified, writes to the standard output (\fBstdout\fP).
+.INDENT 7.0
+.IP \(bu 2
+To output the dump to an archive file, run
+\fI\%mongodump\fP with the \fI\%\-\-archive\fP option and the archive filename.
+.INDENT 2.0
+.INDENT 3.5
 .sp
-To output the dump to an archive file, run \fI\%mongodump\fP with the new
-\fB\-\-archive\fP option and the archive filename.
+.nf
+.ft C
+mongodump \-\-archive=<file>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP \(bu 2
+To output the dump to the standard output stream in order to pipe
+to another process, run \fI\%mongodump\fP with the
+\fI\%\-\-archive\fP option but \fIomit\fP the
+filename.
+.INDENT 2.0
+.INDENT 3.5
 .sp
-To output the dump to the standard output stream in order to pipe to
-another process, run \fI\%mongodump\fP with the \fBarchive\fP option
-but \fIomit\fP the filename.
+.nf
+.ft C
+mongodump \-\-archive
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .sp
-You cannot use the \fB\-\-archive\fP option with the
-\fI\%\-\-out\fP option.
+You cannot use the \fI\%\-\-archive\fP option
+with the \fI\%\-\-out\fP option.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1132,7 +1232,7 @@ and not just a specific database.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-excludeCollection string
+.B \-\-excludeCollection=<string>
 New in version 3.0.
 
 .sp
@@ -1141,7 +1241,7 @@ To exclude multiple collections, specify the \fI\%\-\-excludeCollection\fP multi
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-excludeCollectionsWithPrefix string
+.B \-\-excludeCollectionsWithPrefix=<string>
 New in version 3.0.
 
 .sp
@@ -1151,7 +1251,7 @@ times.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-numParallelCollections int, \-j int
+.B \-\-numParallelCollections=<int>, \-j=<int>
 \fIDefault\fP: 4
 .sp
 Number of collections \fBmongodump\fP should export
@@ -1177,7 +1277,7 @@ is recreated.
 .SS \fBmongodump\fP a Collection
 .sp
 The following operation creates a dump file that contains only the
-collection named \fBcollection\fP in the database named \fBtest\fP\&. In
+collection named \fBrecords\fP in the database named \fBtest\fP\&. In
 this case the database is running on the local interface on port
 \fB27017\fP:
 .INDENT 0.0
@@ -1185,7 +1285,7 @@ this case the database is running on the local interface on port
 .sp
 .nf
 .ft C
-mongodump  \-\-db test \-\-collection collection
+mongodump  \-\-db=test \-\-collection=records
 .ft P
 .fi
 .UNINDENT
@@ -1199,7 +1299,7 @@ except for \fBusers\fP and \fBsalaries\fP:
 .sp
 .nf
 .ft C
-mongodump  \-\-db test \-\-excludeCollection=users \-\-excludeCollection=salaries
+mongodump  \-\-db=test \-\-excludeCollection=users \-\-excludeCollection=salaries
 .ft P
 .fi
 .UNINDENT
@@ -1209,18 +1309,20 @@ mongodump  \-\-db test \-\-excludeCollection=users \-\-excludeCollection=salarie
 In the next example, \fI\%mongodump\fP creates a database dump
 located at \fB/opt/backup/mongodump\-2011\-10\-24\fP, from a database
 running on port \fB37017\fP on the host \fBmongodb1.example.net\fP and
-authenticating using the username \fBuser\fP and the password
-\fBpass\fP, as follows:
+authenticating using the username \fBuser\fP as follows:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongodump \-\-host mongodb1.example.net \-\-port 37017 \-\-username user \-\-password "pass" \-\-out /opt/backup/mongodump\-2011\-10\-24
+mongodump \-\-host=mongodb1.example.net \-\-port=37017 \-\-username=user \-\-authenticationDatabase=admin \-\-out=/opt/backup/mongodump\-2011\-10\-24
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+If you do not include the \fI\%\-\-password\fP,
+\fBmongodump\fP prompts the user for the password.
 .SS Output to an Archive File
 .sp
 New in version 3.2.
@@ -1235,7 +1337,7 @@ of the \fBtest\fP database.
 .sp
 .nf
 .ft C
-mongodump \-\-archive=test.20150715.archive \-\-db test
+mongodump \-\-archive=test.20150715.archive \-\-db=test
 .ft P
 .fi
 .UNINDENT
@@ -1253,7 +1355,7 @@ option but \fIomit\fP the filename:
 .sp
 .nf
 .ft C
-mongodump \-\-archive \-\-db test \-\-port 27017 | mongorestore \-\-archive \-\-port 27018
+mongodump \-\-archive \-\-db=test \-\-port=27017 | mongorestore \-\-archive \-\-port=27018
 .ft P
 .fi
 .UNINDENT
@@ -1277,7 +1379,7 @@ the following operation outputs compressed files into the default
 .sp
 .nf
 .ft C
-mongodump \-\-gzip \-\-db test
+mongodump \-\-gzip \-\-db=test
 .ft P
 .fi
 .UNINDENT
@@ -1291,7 +1393,7 @@ option, specifying the name of the compressed file.
 .sp
 .nf
 .ft C
-mongodump \-\-archive=test.20150715.gz \-\-gzip \-\-db test
+mongodump \-\-archive=test.20150715.gz \-\-gzip \-\-db=test
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongoexport.1 b/debian/mongoexport.1
index cbab4dc4ffb..90fac8e77dd 100644
--- a/debian/mongoexport.1
+++ b/debian/mongoexport.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOEXPORT" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOEXPORT" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongoexport \- MongoDB Export Utility
 .
@@ -35,6 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
 \fI\%Syntax\fP
 .IP \(bu 2
 \fI\%Required Access\fP
@@ -67,6 +69,28 @@ Run \fI\%mongoexport\fP from the system command line, not the \fBmongo\fP shell.
 capability.
 .UNINDENT
 .UNINDENT
+.SH AVAILABILITY
+.sp
+The \fI\%mongoexport\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
 .SH SYNTAX
 .sp
 \fI\%mongoexport\fP must be run directly from the system command line.
@@ -75,7 +99,7 @@ capability.
 .sp
 .nf
 .ft C
-mongoexport \-\-collection <coll> [options]
+mongoexport \-\-collection=<coll> [options]
 .ft P
 .fi
 .UNINDENT
@@ -95,7 +119,7 @@ For example, to export the specified \fI\%collection\fP to the specified \fI\%ou
 .sp
 .nf
 .ft C
-mongoexport \-\-collection events \-\-db reporting \-\-out events.json
+mongoexport \-\-collection=events \-\-db=reporting \-\-out=events.json
 .ft P
 .fi
 .UNINDENT
@@ -110,7 +134,7 @@ Specify the hostname and port in the \fI\%\-\-uri connection string\fP:
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongodb0.example.com:27017/reporting"  \-\-collection events  \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongodb0.example.com:27017/reporting"  \-\-collection=events  \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -127,7 +151,7 @@ Specify the hostname and port in the \fI\%\-\-host\fP:
 .sp
 .nf
 .ft C
-mongoexport \-\-host "mongodb0.example.com:27017" \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="mongodb0.example.com:27017" \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -139,7 +163,7 @@ Specify the hostname and port in the \fI\%\-\-host\fP and \fI\%\-\-port\fP:
 .sp
 .nf
 .ft C
-mongoexport \-\-host "mongodb0.example.com" \-\-port 27017 \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="mongodb0.example.com" \-\-port=27017 \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -158,7 +182,7 @@ Specify the replica set name and members in the \fI\%\-\-uri connection string\f
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -175,7 +199,7 @@ Specify the replica set name and members in the \fI\%\-\-host\fP:
 .sp
 .nf
 .ft C
-mongoexport \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com" \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com" \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -194,7 +218,7 @@ You can specify the read preference in the
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName&readPreference=secondary" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName&readPreference=secondary" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -207,7 +231,7 @@ If specifying the read preference tags, include the
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName&readPreference=secondary&readPreferenceTags=region:east" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/reporting?replicaSet=myReplicaSetName&readPreference=secondary&readPreferenceTags=region:east" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -226,7 +250,7 @@ option. The command\-line option takes a string if specifying only the read pref
 .sp
 .nf
 .ft C
-mongoexport \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference secondary \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference=secondary \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -242,7 +266,7 @@ maxStalenessSeconds:
 .sp
 .nf
 .ft C
-mongoexport \-\-host "myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="myReplicaSetName/mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017" \-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -262,7 +286,7 @@ Specify the hostname of the \fBmongos\fP instance in the
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongos0.example.com:27017/reporting" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongos0.example.com:27017/reporting" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -279,7 +303,7 @@ Specify the hostname and port of the \fBmongos\fP instance in the \fI\%\-\-host\
 .sp
 .nf
 .ft C
-mongoexport \-\-host "mongos0.example.com:27017" \-\-collection events \-\-db reporting \-\-out events.json[additional options]
+mongoexport \-\-host="mongos0.example.com:27017" \-\-collection=events \-\-db=reporting \-\-out=events.json[additional options]
 .ft P
 .fi
 .UNINDENT
@@ -298,7 +322,7 @@ You can specify the read preference in the
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongos0.example.com:27017/reporting?readPreference=secondary" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongos0.example.com:27017/reporting?readPreference=secondary" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -311,7 +335,7 @@ If specifying the read preference tags, include the
 .sp
 .nf
 .ft C
-mongoexport \-\-uri "mongodb://mongos0.example.com:27017/reporting?readPreference=secondary&readPreferenceTags=region:east" \-\-collection events \-\-out events.json [additional options]
+mongoexport \-\-uri="mongodb://mongos0.example.com:27017/reporting?readPreference=secondary&readPreferenceTags=region:east" \-\-collection=events \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -330,7 +354,7 @@ option.  The command\-line option takes a string if specifying only the read pre
 .sp
 .nf
 .ft C
-mongoexport \-\-host "mongos0.example.com:27017" \-\-readPreference secondary \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="mongos0.example.com:27017" \-\-readPreference=secondary \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -346,7 +370,7 @@ maxStalenessSeconds:
 .sp
 .nf
 .ft C
-mongoexport \-\-host "mongos0.example.com:27017" \-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq \-\-collection events \-\-db reporting \-\-out events.json [additional options]
+mongoexport \-\-host="mongos0.example.com:27017" \-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ]}\(aq \-\-collection=events \-\-db=reporting \-\-out=events.json [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -387,13 +411,20 @@ kind of functionality.
 .UNINDENT
 .UNINDENT
 .sp
-To preserve type information, \fI\%mongoexport\fP and \fBmongoimport\fP
-uses the strict mode representation
-for certain types.
+Starting in version 4.2, \fI\%mongoexport\fP:
+.INDENT 0.0
+.IP \(bu 2
+Outputs data in Extended JSON v2.0 (Relaxed mode) by default.
+.IP \(bu 2
+Outputs Extended JSON v2.0 (Canonical mode) if used with
+\fI\%\-\-jsonFormat\fP\&.
+.UNINDENT
+.sp
+Earlier versions used Extended JSON v1.0 (Canonical mode)\&.
 .sp
 For example, the following insert operation in the \fBmongo\fP
-shell uses the shell mode representation for the BSON types
-\fBdata_date\fP and \fBdata_numberlong\fP:
+shell uses the various shell helpers for the
+BSON types Date and 64\-bit integer:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -406,7 +437,7 @@ db.traffic.insert( { _id: 1, volume: NumberLong(\(aq2980000\(aq), date: new Date
 .UNINDENT
 .UNINDENT
 .sp
-The argument to \fBdata_numberlong\fP must be quoted to avoid potential
+The argument to 64\-bit integer must be quoted to avoid potential
 loss of accuracy.
 .sp
 Use \fI\%mongoexport\fP to export the data:
@@ -415,26 +446,63 @@ Use \fI\%mongoexport\fP to export the data:
 .sp
 .nf
 .ft C
-mongoexport \-\-db test \-\-collection traffic \-\-out traffic.json
+mongoexport \-\-db=test \-\-collection=traffic \-\-out=traffic.json
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-The exported data is in strict mode representation to preserve type information:
+In version 4.2+, the exported data is in Extended JSON v2.0
+(Relaxed mode)\&.
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-{ "_id" : 1, "volume" : { "$numberLong" : "2980000" }, "date" : { "$date" : "2014\-03\-13T13:47:42.483\-0400" } }
+{"_id":1.0,"volume":2980000,"date":{"$date":"2019\-08\-05T16:18:29.559Z"}}
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-See /reference/mongodb\-extended\-json for a complete list of
-these types and the representations used.
+To output in Extended JSON v2.0 (Canonical
+mode), include the
+\fI\%\-\-jsonFormat=canonical\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoexport \-\-db=test \-\-collection=traffic \-\-jsonFormat=canonical \-\-out=traffic.json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The exported data is in Extended JSON v2.0 (Canonical
+mode):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{"_id":{"$numberDouble":"1.0"},"volume":{"$numberLong":"2980000"},"date":{"$date":{"$numberLong":"1565363188675"}}}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+In version 4.0 and earlier, the exported data is in Extended JSON v1.0 (Strict mode)
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{"_id":1.0,"volume":{"$numberLong":"2980000"},"date":{"$date":"2019\-08\-05T16:18:29.559Z"}}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .SS FIPS
 .sp
 Starting in version 4.2, MongoDB removes the \fB\-\-sslFIPSMode\fP
@@ -509,7 +577,7 @@ Returns the \fBmongoexport\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -520,7 +588,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -568,7 +636,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>, \-h <hostname><:port>
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
 \fIDefault\fP: localhost:27017
 .sp
 Specifies a resolvable hostname for the \fBmongod\fP to which to
@@ -583,7 +651,7 @@ the following:
 .sp
 .nf
 .ft C
-\-\-host <replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
+\-\-host=<replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
@@ -599,7 +667,7 @@ the host and port of only that member:
 .sp
 .nf
 .ft C
-\-\-host <hostname1><:port>
+\-\-host=<hostname1><:port>
 .ft P
 .fi
 .UNINDENT
@@ -619,7 +687,7 @@ You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -657,7 +725,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -698,7 +766,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -717,7 +785,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
@@ -736,7 +804,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -768,8 +836,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -812,7 +878,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
+.B \-\-username=<username>, \-u=<username>
 Specifies a username with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -826,7 +892,7 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
+.B \-\-password=<password>, \-p=<password>
 Specifies a password with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -846,7 +912,7 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
+.B \-\-authenticationDatabase=<dbname>
 Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
 See user\-authentication\-database\&.
 .sp
@@ -862,7 +928,7 @@ assumes that the database specified to export holds the user\(aqs credentials.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongoexport\fP instance uses to
@@ -937,7 +1003,7 @@ You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiServiceName
+.B \-\-gssapiServiceName=<serviceName>
 New in version 2.6.
 
 .sp
@@ -948,7 +1014,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiHostName
+.B \-\-gssapiHostName=<hostname>
 New in version 2.6.
 
 .sp
@@ -959,7 +1025,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-db <database>, \-d <database>
+.B \-\-db=<database>, \-d=<database>
 Specifies the name of the database on which to run the \fBmongoexport\fP\&.
 .sp
 \fBNOTE:\fP
@@ -971,12 +1037,12 @@ You cannot specify both \fI\%\-\-db\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-collection <collection>, \-c <collection>
+.B \-\-collection=<collection>, \-c=<collection>
 Specifies the collection to export.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-fields <field1[,field2]>, \-f <field1[,field2]>
+.B \-\-fields=<field1[,field2]>, \-f=<field1[,field2]>
 Specifies a field or fields to \fIinclude\fP in the export. Use a comma
 separated list of fields to specify multiple fields.
 .sp
@@ -999,7 +1065,7 @@ See: \fI\%Export Data in CSV Format using \-\-fields option\fP for sample usage.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-fieldFile <filename>
+.B \-\-fieldFile=<filename>
 An alternative to \fI\%\-\-fields\fP\&. The
 \fI\%\-\-fieldFile\fP option allows you to
 specify in a file the field or fields to \fIinclude\fP in the export and is
@@ -1015,14 +1081,18 @@ See \fI\%Use a File to Specify the Fields to Export in CSV Format\fP for sample
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-query <JSON>, \-q <JSON>
+.B \-\-query=<JSON>, \-q=<JSON>
 Provides a query as a JSON document (enclosed in quotes) to
-return matching documents in the export. Specify JSON in strict
-format\&.
+return matching documents in the export.
 .sp
 You must enclose the query document in single quotes (\fB\(aq{ ... }\(aq\fP) to ensure that it does
 not interact with your shell environment.
 .sp
+Starting in MongoDB 4.2, the query \fBmust\fP be in
+Extended JSON v2 format (either relaxed or canonical/strict
+mode), including enclosing the
+field names and operators in quotes:
+.sp
 For example, given a collection named \fBrecords\fP in the database
 \fBtest\fP with the following documents:
 .INDENT 7.0
@@ -1041,17 +1111,18 @@ For example, given a collection named \fBrecords\fP in the database
 .UNINDENT
 .UNINDENT
 .sp
-The following \fI\%mongoexport\fP uses the \fI\%\-q\fP option to
-export only the documents with the field \fBa\fP greater than or equal to
-(\fB$gte\fP) to \fB3\fP and the field \fBdate\fP less than
-\fBISODate("2016\-01\-01T00:00:00Z")\fP (using the strict format
-for dates { "$date": "YYYY\-MM\-DDTHH:mm:ss.mmm<offset>"}):
+The following \fI\%mongoexport\fP uses the \fI\%\-q\fP option
+to export only the documents with the field \fBa\fP greater than or
+equal to (\fB$gte\fP) to \fB3\fP and the field \fBdate\fP less than
+\fBISODate("2016\-01\-01T00:00:00Z")\fP (using the extended JSON v2
+format (relaxed mode) for dates { "$date":
+"YYYY\-MM\-DDTHH:mm:ss.mmm<offset>"}):
 .INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongoexport \-d test \-c records \-q \(aq{ a: { $gte: 3 }, date: { $lt: { "$date": "2016\-01\-01T00:00:00.000Z" } } }\(aq \-\-out exportdir/myRecords.json
+mongoexport \-d=test \-c=records \-q=\(aq{ "a": { "$gte": 3 }, "date": { "$lt": { "$date": "2016\-01\-01T00:00:00.000Z" } } }\(aq \-\-out=exportdir/myRecords.json
 .ft P
 .fi
 .UNINDENT
@@ -1075,7 +1146,7 @@ You can sort the results with the \fI\%\-\-sort\fP option to
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-type <string>
+.B \-\-type=<string>
 \fIDefault\fP: json
 .sp
 New in version 3.0.
@@ -1090,13 +1161,24 @@ declare the fields to export from the collection.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-out <file>, \-o <file>
+.B \-\-out=<file>, \-o=<file>
 Specifies a file to write the export to. If you do not specify a file
 name, the \fI\%mongoexport\fP writes data to standard output
 (e.g. \fBstdout\fP).
 .UNINDENT
 .INDENT 0.0
 .TP
+.B \-\-jsonFormat=<canonical|relaxed>
+\fIDefault\fP: relaxed
+.sp
+Modifies the output to use either canonical or relaxed mode of the
+/reference/mongodb\-extended\-json format.
+.sp
+For differences between canonical and relaxed modes, see
+/reference/mongodb\-extended\-json\&.
+.UNINDENT
+.INDENT 0.0
+.TP
 .B \-\-jsonArray
 Modifies the output of \fI\%mongoexport\fP to write the
 entire contents of the export as a single JSON array. By
@@ -1149,7 +1231,7 @@ inconsistencies, duplicates, or result in missed documents.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-readPreference <string|document>
+.B \-\-readPreference=<string|document>
 \fIDefault\fP: \fBprimary\fP
 .sp
 Specifies the read preference for
@@ -1162,7 +1244,7 @@ A string if specifying only the read preference mode:
 .sp
 .nf
 .ft C
-\-\-readPreference secondary
+\-\-readPreference=secondary
 .ft P
 .fi
 .UNINDENT
@@ -1176,7 +1258,7 @@ optional maxStalenessSeconds:
 .sp
 .nf
 .ft C
-\-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
+\-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
 .ft P
 .fi
 .UNINDENT
@@ -1233,21 +1315,21 @@ and consideration.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-skip <number>
+.B \-\-skip=<number>
 Use \fI\%\-\-skip\fP to control where \fI\%mongoexport\fP begins
 exporting documents. See \fBskip()\fP for information about
 the underlying operation.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-limit <number>
+.B \-\-limit=<number>
 Specifies a maximum number of documents to include in the
 export. See \fBlimit()\fP for information about
 the underlying operation.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sort <JSON>
+.B \-\-sort=<JSON>
 Specifies an ordering for exported results. If an index does
 \fBnot\fP exist that can support the sort operation, the results must
 be \fIless than\fP 32 megabytes.
@@ -1259,9 +1341,9 @@ Use \fI\%\-\-sort\fP conjunction with \fI\%\-\-skip\fP and
 .sp
 .nf
 .ft C
-mongoexport \-d test \-c records \-\-sort \(aq{a: 1}\(aq \-\-limit 100 \-\-out export.0.json
-mongoexport \-d test \-c records \-\-sort \(aq{a: 1}\(aq \-\-limit 100 \-\-skip 100 \-\-out export.1.json
-mongoexport \-d test \-c records \-\-sort \(aq{a: 1}\(aq \-\-limit 100 \-\-skip 200 \-\-out export.2.json
+mongoexport \-d=test \-c=records \-\-sort=\(aq{a: 1}\(aq \-\-limit=100 \-\-out=export.0.json
+mongoexport \-d=test \-c=records \-\-sort=\(aq{a: 1}\(aq \-\-limit=100 \-\-skip=100 \-\-out=export.1.json
+mongoexport \-d=test \-c=records \-\-sort=\(aq{a: 1}\(aq \-\-limit=100 \-\-skip=200 \-\-out=export.2.json
 .ft P
 .fi
 .UNINDENT
@@ -1294,7 +1376,7 @@ to export.
 .sp
 .nf
 .ft C
-mongoexport \-\-db users \-\-collection contacts \-\-type=csv \-\-fields name,address \-\-out /opt/backups/contacts.csv
+mongoexport \-\-db=users \-\-collection=contacts \-\-type=csv \-\-fields=name,address \-\-out=/opt/backups/contacts.csv
 .ft P
 .fi
 .UNINDENT
@@ -1340,7 +1422,7 @@ the file:
 .sp
 .nf
 .ft C
-mongoexport \-\-db users \-\-collection contacts \-\-type=csv \-\-fieldFile fields.txt \-\-out /opt/backups/contacts.csv
+mongoexport \-\-db=users \-\-collection=contacts \-\-type=csv \-\-fieldFile=fields.txt \-\-out=/opt/backups/contacts.csv
 .ft P
 .fi
 .UNINDENT
@@ -1360,7 +1442,7 @@ of the field names as the first line:
 .sp
 .nf
 .ft C
-mongoexport \-\-db users \-\-collection contacts \-\-type csv \-\-fields name,address \-\-noHeaderLine \-\-out /opt/backups/contacts.csv
+mongoexport \-\-db=users \-\-collection=contacts \-\-type=csv \-\-fields=name,address \-\-noHeaderLine \-\-out=/opt/backups/contacts.csv
 .ft P
 .fi
 .UNINDENT
@@ -1388,7 +1470,7 @@ writes the export to the \fBcontacts.json\fP file in JSON format.
 .sp
 .nf
 .ft C
-mongoexport \-\-db sales \-\-collection contacts \-\-out contacts.json
+mongoexport \-\-db=sales \-\-collection=contacts \-\-out=contacts.json
 .ft P
 .fi
 .UNINDENT
@@ -1429,7 +1511,7 @@ have \fBmongoexport\fP prompt for the password:
 .sp
 .nf
 .ft C
-mongoexport \-\-host mongodb1.example.net \-\-port 27017 \-\-username someUser \-\-authenticationDatabase admin \-\-collection contacts \-\-db marketing \-\-out mdb1\-examplenet.json
+mongoexport \-\-host=mongodb1.example.net \-\-port=27017 \-\-username=someUser \-\-authenticationDatabase=admin \-\-collection=contacts \-\-db=marketing \-\-out=mdb1\-examplenet.json
 .ft P
 .fi
 .UNINDENT
@@ -1449,7 +1531,7 @@ for the password:
 .sp
 .nf
 .ft C
-mongoexport \-\-uri \(aqmongodb://someUser@mongodb0.example.com:27017/marketing?authsource=admin\(aq \-\-collection contacts \-\-out mdb1\-examplenet.json
+mongoexport \-\-uri=\(aqmongodb://someUser@mongodb0.example.com:27017/marketing?authsource=admin\(aq \-\-collection=contacts \-\-out=mdb1\-examplenet.json
 .ft P
 .fi
 .UNINDENT
@@ -1463,14 +1545,14 @@ database using the "\fI\%\-\-db\fP" option.
 For instance, this command returns all documents in the \fBsales\fP
 database\(aqs \fBcontacts\fP collection that contain a field named \fBdept\fP
 equal to \fB"ABC"\fP and the field \fBdate\fP greater than or equal to
-ISODate("2018\-01\-01") (using the strict format for dates
+ISODate("2018\-01\-01") (using the canonical format for dates
 { "$date": "YYYY\-MM\-DDTHH:mm:ss.mmm<offset>"} )
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongoexport \-\-db sales \-\-collection contacts \-\-query \(aq{"dept": "ABC", date: { $gte: { "$date": "2018\-01\-01T00:00:00.000Z" } }}\(aq
+mongoexport \-\-db=sales \-\-collection=contacts \-\-query=\(aq{"dept": "ABC", date: { $gte: { "$date": "2018\-01\-01T00:00:00.000Z" } }}\(aq
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongofiles.1 b/debian/mongofiles.1
index 742fd9d7af5..ba9d9ea6a7d 100644
--- a/debian/mongofiles.1
+++ b/debian/mongofiles.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOFILES" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOFILES" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongofiles \- MongoDB GridFS Utility
 .
@@ -35,6 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
 \fI\%Required Access\fP
 .IP \(bu 2
 \fI\%Behavior\fP
@@ -95,6 +97,28 @@ For replica sets,
 primary\&.
 .UNINDENT
 .UNINDENT
+.SH AVAILABILITY
+.sp
+The \fI\%mongofiles\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
 .SH REQUIRED ACCESS
 .sp
 In order to connect to a \fBmongod\fP that enforces authorization
@@ -185,7 +209,7 @@ Returns the \fBmongofiles\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -196,7 +220,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -244,7 +268,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>
+.B \-\-host=<hostname><:port>
 Specifies a resolvable hostname for the \fBmongod\fP that holds
 your GridFS system. By default \fI\%mongofiles\fP attempts to connect
 to a MongoDB process running on the localhost port number \fB27017\fP\&.
@@ -261,7 +285,7 @@ You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -299,7 +323,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -340,7 +364,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -359,7 +383,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
@@ -378,7 +402,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -410,8 +434,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -454,7 +476,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
+.B \-\-username=<username>, \-u=<username>
 Specifies a username with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -468,7 +490,7 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
+.B \-\-password=<password>, \-p=<password>
 Specifies a password with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -488,7 +510,7 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
+.B \-\-authenticationDatabase=<dbname>
 Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
 See user\-authentication\-database\&.
 .sp
@@ -501,7 +523,7 @@ You cannot specify both \fI\%\-\-authenticationDatabase\fP and \fI\%\-\-uri\fP\&
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongofiles\fP instance uses to
@@ -576,7 +598,7 @@ You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiServiceName
+.B \-\-gssapiServiceName=<serviceName>
 New in version 2.6.
 
 .sp
@@ -587,7 +609,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiHostName
+.B \-\-gssapiHostName=<hostname>
 New in version 2.6.
 
 .sp
@@ -598,7 +620,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-db <database>, \-d <database>
+.B \-\-db=<database>, \-d=<database>
 Specifies the name of the database on which to run the \fBmongofiles\fP\&.
 .sp
 \fBNOTE:\fP
@@ -610,7 +632,7 @@ You cannot specify both \fI\%\-\-db\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-local <filename>, \-l <filename>
+.B \-\-local=<filename>, \-l=<filename>
 Specifies the local filesystem name of a file for get and put
 operations.
 .sp
@@ -622,7 +644,7 @@ default.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-type <MIME>
+.B \-\-type=<MIME>
 Provides the ability to specify a MIME type to describe the file
 inserted into GridFS storage. \fI\%mongofiles\fP omits this option in
 the default operation.
@@ -641,14 +663,14 @@ In the default operation, files will not be overwritten by a
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-prefix string
+.B \-\-prefix=<string>
 \fIDefault\fP: fs
 .sp
 GridFS prefix to use.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-writeConcern <document>
+.B \-\-writeConcern=<document>
 \fIDefault\fP: majority
 .sp
 Specifies the write concern for each write operation that \fBmongofiles\fP
@@ -660,7 +682,7 @@ Specify the write concern as a document with w options:
 .sp
 .nf
 .ft C
-\-\-writeConcern "{w:\(aqmajority\(aq}"
+\-\-writeConcern="{w:\(aqmajority\(aq}"
 .ft P
 .fi
 .UNINDENT
@@ -673,7 +695,7 @@ the URI string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-readPreference <string|document>
+.B \-\-readPreference=<string|document>
 \fIDefault\fP: \fBprimary\fP
 .sp
 Specifies the read preference for
@@ -686,7 +708,7 @@ A string if specifying only the read preference mode:
 .sp
 .nf
 .ft C
-\-\-readPreference secondary
+\-\-readPreference=secondary
 .ft P
 .fi
 .UNINDENT
@@ -700,7 +722,7 @@ optional maxStalenessSeconds:
 .sp
 .nf
 .ft C
-\-\-readPreference \(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
+\-\-readPreference=\(aq{mode: "secondary", tagSets: [ { "region": "east" } ], maxStalenessSeconds: 120}\(aq
 .ft P
 .fi
 .UNINDENT
@@ -767,14 +789,25 @@ different location for the file on the local file system, use the
 .UNINDENT
 .INDENT 0.0
 .TP
-.B get_id "<ObjectId>"
+.B get_id "<_id>"
 New in version 3.2.0.
 
 .sp
-Copy the specified file from GridFS storage to the local file system.
+Copy the file, specified by its \fB<_id>\fP, from GridFS storage to the
+local file system.
 .sp
-Here \fB<ObjectId>\fP refers to the extended JSON \fB_id\fP of the
-object in GridFS. \fI\%mongofiles\fP writes the file to the local
+Here \fB<_id>\fP refers to the extended JSON \fB_id\fP of the
+object in GridFS:
+.INDENT 7.0
+.IP \(bu 2
+Starting in MongoDB 4.2, \fBget_id\fP can accept either ObjectId
+values or non\-ObjectId values for \fB<_id>\fP\&.
+.IP \(bu 2
+In MongoDB 4.0 and earlier, \fBget_id\fP only
+accepts \fB<ObjectId>\fP values.
+.UNINDENT
+.sp
+\fI\%mongofiles\fP writes the file to the local
 file system using the file\(aqs \fBfilename\fP in GridFS. To choose a
 different location for the file on the local file system, use the
 \fI\%\-\-local\fP option.
@@ -786,12 +819,19 @@ Delete the specified file from GridFS storage.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B delete_id "<ObjectId>"
+.B delete_id "<_id>"
 New in version 3.2.0.
 
 .sp
-Delete the specified file from GridFS storage. Specify the file using
-its \fB_id\fP\&.
+Delete the file, specified by its \fB<_id>\fP, from GridFS storage:
+.INDENT 7.0
+.IP \(bu 2
+Starting in MongoDB 4.2, \fBdelete_id\fP can accept
+either ObjectId values or non\-ObjectId values for \fB<_id>\fP\&.
+.IP \(bu 2
+In MongoDB 4.0 and earlier, \fBdelete_id\fP only
+accepts \fB<ObjectId>\fP values.
+.UNINDENT
 .UNINDENT
 .SH EXAMPLES
 .sp
@@ -802,7 +842,7 @@ To return a list of all files in a GridFS collection in the
 .sp
 .nf
 .ft C
-mongofiles \-d records list
+mongofiles \-d=records list
 .ft P
 .fi
 .UNINDENT
@@ -817,9 +857,9 @@ hostname, and issue a command that resembles one of the following:
 .sp
 .nf
 .ft C
-mongofiles \-\-port 37017 \-d records list
-mongofiles \-\-host db1.example.net \-d records list
-mongofiles \-\-host db1.example.net \-\-port 37017 \-d records list
+mongofiles \-\-port=37017 \-d=records list
+mongofiles \-\-host=db1.example.net \-d=records list
+mongofiles \-\-host=db1.example.net \-\-port=37017 \-d=records list
 .ft P
 .fi
 .UNINDENT
@@ -835,7 +875,7 @@ the \fBrecords\fP database, you can use the following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records put 32\-corinth.lp
+mongofiles \-d=records put 32\-corinth.lp
 .ft P
 .fi
 .UNINDENT
@@ -848,7 +888,7 @@ the \fBrecords\fP database, you can use the following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records delete 32\-corinth.lp
+mongofiles \-d=records delete 32\-corinth.lp
 .ft P
 .fi
 .UNINDENT
@@ -862,7 +902,7 @@ following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records search corinth
+mongofiles \-d=records search corinth
 .ft P
 .fi
 .UNINDENT
@@ -875,7 +915,7 @@ that begin with the string \fB32\fP, you can use the following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records list 32
+mongofiles \-d=records list 32
 .ft P
 .fi
 .UNINDENT
@@ -888,7 +928,7 @@ database named \fB32\-corinth.lp\fP, you can use the following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records get 32\-corinth.lp
+mongofiles \-d=records get 32\-corinth.lp
 .ft P
 .fi
 .UNINDENT
@@ -902,7 +942,7 @@ the following command:
 .sp
 .nf
 .ft C
-mongofiles \-d records get_id \(aqObjectId("56feac751f417d0357e7140f")\(aq
+mongofiles \-d=records get_id \(aqObjectId("56feac751f417d0357e7140f")\(aq
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongoimport.1 b/debian/mongoimport.1
index c494b85d758..dc5ffb93aa9 100644
--- a/debian/mongoimport.1
+++ b/debian/mongoimport.1
@@ -1,8 +1,8 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOIMPORT" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOIMPORT" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
-mongoimport \- MongoDB LDAP Configuration Testing Utility
+mongoimport \- MongoDB Import Utility
 .
 .nr rst2man-indent-level 0
 .
@@ -35,683 +35,1435 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
-\fI\%Usage\fP
+\fI\%Availability\fP
+.IP \(bu 2
+\fI\%Behavior\fP
+.IP \(bu 2
+\fI\%Required Access\fP
 .IP \(bu 2
 \fI\%Options\fP
+.IP \(bu 2
+\fI\%Examples\fP
 .UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+.IP "macOS Sierra and Go 1.6 Incompatibility"
 .sp
-New in version 3.4: MongoDB Enterprise
-
+Users running on macOS Sierra require the 3.2.10 or newer version
+of  mongoimport\&.
+.UNINDENT
+.UNINDENT
 .SH SYNOPSIS
 .sp
-Starting in version 3.4, MongoDB Enterprise provides
-\fI\%mongoldap\fP for testing MongoDB\(aqs LDAP configuration
-options against a running LDAP server or set
-of servers.
-.sp
-To validate the LDAP options in the configuration file, set the
-\fI\%mongoldap\fP \fI\%\-\-config\fP option to the configuration file\(aqs
-path.
+The \fI\%mongoimport\fP tool imports content from an
+Extended JSON, CSV, or TSV export
+created by \fBmongoexport\fP, or potentially, another third\-party export
+tool.
 .sp
-To test the LDAP configuration options, you must specify a \fI\%\-\-user\fP
-and \fB\-\-password\fP\&. \fI\%mongoldap\fP simulates authentication to a
-MongoDB server running with the provided configuration options and credentials.
+See the mongoexport document for more information regarding
+\fBmongoexport\fP, which provides the inverse "exporting"
+capability.
 .sp
-\fI\%mongoldap\fP returns a report that includes the success or failure of
-any step in the LDAP authentication or authorization procedure. Error messages
-include information on specific errors encountered and potential advice for
-resolving the error.
+Run \fI\%mongoimport\fP from the system command line, not the \fBmongo\fP shell.
+.SH AVAILABILITY
 .sp
-When configuring options related to LDAP authorization, \fI\%mongoldap\fP executes an LDAP query
-constructed using the provided configuration options and username, and returns
-a list of roles on the \fBadmin\fP database which the user is authorized for.
+The \fI\%mongoimport\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
 .sp
-You can use this information when configuring LDAP authorization roles for user access control. For example, use
-\fI\%mongoldap\fP to ensure your configuration allows privileged users to
-gain the necessary roles to perform their expected tasks. Similarly, use
-\fI\%mongoldap\fP to ensure your configuration disallows non\-privileged
-users from gaining roles for accessing the MongoDB server, or performing
-unauthorized actions.
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
 .sp
-When configuring options related to LDAP authentication, use \fI\%mongoldap\fP to ensure that the authentication
-operation works as expected.
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
+.SH BEHAVIOR
 .sp
-Run \fI\%mongoldap\fP from the system command line, not the \fBmongo\fP shell.
+\fBWARNING:\fP
+.INDENT 0.0
+.INDENT 3.5
+Avoid using \fI\%mongoimport\fP and \fBmongoexport\fP for
+full instance production backups. They do not reliably preserve all rich
+BSON data types, because JSON can only represent a subset
+of the types supported by BSON. Use \fBmongodump\fP
+and \fBmongorestore\fP as described in /core/backups for this
+kind of functionality.
+.UNINDENT
+.UNINDENT
+.SS JSON Format
 .sp
-This document provides a complete overview of all command line options for
-\fI\%mongoldap\fP\&.
-.SH USAGE
+Starting in MongoDB 4.2, \fI\%mongoimport\fP expects import data
+to be in Extended JSON v2.0 (either Relaxed or Canonical mode)
+by default. To recognize data that is in Extended JSON v1.0 format, see
+\fI\%\-\-legacy\fP\&.
 .sp
-\fBNOTE:\fP
+In earlier versions, \fI\%mongoimport\fP expects data in
+/reference/mongodb\-extended\-json\-v1 format.
 .INDENT 0.0
 .INDENT 3.5
-A full description of LDAP or Active Directory is beyond the scope of
-this documentation.
+.SS Tip
+.sp
+In general, the versions of \fBmongoexport\fP and
+\fI\%mongoimport\fP should match. That is, to import data
+created from \fBmongoexport\fP, you should use the
+corresponding version of \fI\%mongoimport\fP\&.
 .UNINDENT
 .UNINDENT
+.SS Encoding
+.sp
+\fI\%mongoimport\fP only supports data files that are UTF\-8 encoded.
+Using other encodings will produce errors.
+.SS FIPS
+.sp
+Starting in version 4.2, MongoDB removes the \fB\-\-sslFIPSMode\fP
+option for mongoimport\&. mongoimport
+will use FIPS compliant connections to
+\fBmongod\fP/\fBmongos\fP if the
+\fBmongod\fP/\fBmongos\fP instances are
+configured to use FIPS mode\&.
+.SS Write Concern
+.sp
+Starting in version 4.2, if you specify write concern in both the
+\fI\%\-\-writeConcern\fP option and the
+\fI\%\-\-uri connection string\fP option, the
+\fI\%\-\-writeConcern\fP value overrides
+the write concern specified in the URI string.
+.sp
+In earlier versions, the two options are incompatible.
+.SS Batches
+.sp
+Starting in MongoDB 4.2, \fI\%mongoimport\fP uses maximum batch
+size of 100,000 to perform bulk insert/upsert operations.
+.SH REQUIRED ACCESS
+.sp
+In order to connect to a \fBmongod\fP that enforces authorization
+with the \fB\-\-auth\fP option, you must use the
+\fB\-\-username\fP and \fB\-\-password\fP options. The connecting user must
+possess, at a minimum, the \fBreadWrite\fP role on the database
+into which they are importing data.
+.SH OPTIONS
+.sp
+Changed in version 3.0.0: \fI\%mongoimport\fP removed the \fB\-\-dbpath\fP as well as related
+\fB\-\-directoryperdb\fP and \fB\-\-journal\fP options. To use
+\fI\%mongoimport\fP, you must run \fI\%mongoimport\fP against a running
+\fBmongod\fP or \fBmongos\fP instance as appropriate.
+
+.INDENT 0.0
+.TP
+.B mongoimport
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-help
+Returns information on the options and use of \fBmongoimport\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-verbose, \-v
+Increases the amount of internal reporting returned on standard output
+or in log files. Increase the verbosity with the \fB\-v\fP form by
+including the option multiple times, (e.g. \fB\-vvvvv\fP\&.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-quiet
+Runs \fBmongoimport\fP in a quiet mode that attempts to limit the amount
+of output.
 .sp
-Consider the following sample configuration file, designed to support
-LDAP authentication and authorization via Active Directory:
+This option suppresses:
+.INDENT 7.0
+.IP \(bu 2
+output from database commands
+.IP \(bu 2
+replication activity
+.IP \(bu 2
+connection accepted events
+.IP \(bu 2
+connection closed events
+.UNINDENT
+.UNINDENT
 .INDENT 0.0
+.TP
+.B \-\-version
+Returns the \fBmongoimport\fP release number.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-uri=<connectionString>
+New in version 3.4.6.
+
+.sp
+Specify a resolvable URI
+connection string (enclose in quotes) to connect to the MongoDB deployment.
+.INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-security:
-   authorization: "enabled"
-   ldap:
-      servers: "activedirectory.example.net"
-      bind:
-         queryUser: "mongodbadmin@dba.example.com"
-         queryPassword: "secret123"
-      userToDNMapping:
-         \(aq[
-            {
-               match : "(.+)",
-               ldapQuery: "DC=example,DC=com??sub?(userPrincipalName={0})"
-            }
-         ]\(aq
-      authz:
-         queryTemplate: "DC=example,DC=com??sub?(&(objectClass=group)(member:1.2.840.113556.1.4.1941:={USER}))"
-setParameter:
-   authenticationMechanisms: "PLAIN"
+\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-You can use \fI\%mongoldap\fP to validate the configuration file, which
-returns a report of the procedure. You must specify a username and password
-for \fI\%mongoldap\fP\&.
+For information on the components of the connection string, see
+the Connection String URI Format documentation.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+For TLS/SSL options, use the command\-line options instead of the
+URI options for TLS/SSL (Available starting in
+4.2)\&.
+.UNINDENT
+.UNINDENT
+.sp
+\fBIMPORTANT:\fP
+.INDENT 7.0
+.INDENT 3.5
+The following command\-line options cannot be used in conjunction
+with \fI\%\-\-uri\fP option:
 .INDENT 0.0
+.IP \(bu 2
+\fI\%\-\-host\fP
+.IP \(bu 2
+\fI\%\-\-port\fP
+.IP \(bu 2
+\fI\%\-\-db\fP
+.IP \(bu 2
+\fI\%\-\-username\fP
+.IP \(bu 2
+\fI\%\-\-password\fP  (if the
+URI connection string also includes the password)
+.IP \(bu 2
+\fI\%\-\-authenticationDatabase\fP
+.IP \(bu 2
+\fI\%\-\-authenticationMechanism\fP
+.UNINDENT
+.sp
+Instead, specify these options as part of your \fI\%\-\-uri\fP
+connection string.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
+\fIDefault\fP: localhost:27017
+.sp
+Specifies a resolvable hostname for the \fBmongod\fP to which to
+connect. By default, the \fBmongoimport\fP attempts to connect to a MongoDB
+instance running on the localhost on port number \fB27017\fP\&.
+.sp
+To connect to a replica set, specify the
+\fBreplSetName\fP and a seed list of set members, as in
+the following:
+.INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongoldap \-\-config <path\-to\-config> \-\-user "bob@dba.example.com" \-\-password "secret123"
+\-\-host=<replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-If the provided credentials are valid, and the LDAP options in the
-configuration files are valid, the output might be as follows:
-.INDENT 0.0
+When specifying the replica set list format, \fBmongoimport\fP always connects to
+the primary\&.
+.sp
+You can also connect to any single member of the replica set by specifying
+the host and port of only that member:
+.INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-Checking that an LDAP server has been specified...
-[OK] LDAP server found
-
-Connecting to LDAP server...
-[OK] Connected to LDAP server
-
-Parsing MongoDB to LDAP DN mappings..
-[OK] MongoDB to LDAP DN mappings appear to be valid
-
-Attempting to authenticate against the LDAP server...
-[OK] Successful authentication performed
-
-Checking if LDAP authorization has been enabled by configuration...
-[OK] LDAP authorization enabled
-
-Parsing LDAP query template..
-[OK] LDAP query configuration template appears valid
-
-Executing query against LDAP server...
-[OK] Successfully acquired the following roles:
-\&...
+\-\-host=<hostname1><:port>
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.SH OPTIONS
+.sp
+Changed in version 3.0.0: If you use IPv6 and use the \fB<address>:<port>\fP format, you must
+enclose the portion of an address and port combination in
+brackets (e.g. \fB[<address>]\fP).
+
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-config <filename>, \-f <filename>
-Specifies a configuration file for runtime configuration options.
-The options are equivalent to the command\-line
-configuration options. See /reference/configuration\-options for
-more information.
+.B \-\-port=<port>
+\fIDefault\fP: 27017
 .sp
-\fBmongoldap\fP uses any configuration options related to security\-ldap
-or security\-ldap\-external for testing LDAP authentication or
-authorization.
+Specifies the TCP port on which the MongoDB instance listens for
+client connections.
 .sp
-Requires specifying \fI\%\-\-user\fP\&. May accept \fI\%\-\-password\fP for
-testing LDAP authentication.
-.sp
-Ensure the configuration file uses ASCII encoding. The \fBmongoldap\fP
-instance does not support configuration files with non\-ASCII encoding,
-including UTF\-8.
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+You cannot specify both \fI\%\-\-port\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-user <string>
-Username for \fBmongoldap\fP to use when attempting LDAP authentication or
-authorization.
+.B \-\-ipv6
+\fIRemoved in version 3.0.\fP
+.sp
+Enables IPv6 support and allows \fBmongoimport\fP to connect to the
+MongoDB instance using an IPv6 network. Prior to MongoDB 3.0, you
+had to specify \fI\%\-\-ipv6\fP to use IPv6. In MongoDB 3.0 and later, IPv6
+is always enabled.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <string>
-Password of the \fB\-\-user\fP for \fBmongoldap\fP to use when attempting LDAP
-authentication. Not required for LDAP authorization.
+.B \-\-ssl
+New in version 2.6.
+
+.sp
+Enables connection to a \fBmongod\fP or \fBmongos\fP that has
+TLS/SSL support enabled.
+.sp
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapServers <host1>:<port>,<host2>:<port>,...,<hostN>:<port>
-New in version 3.4: Available in MongoDB Enterprise only.
+.B \-\-sslCAFile=<filename>
+New in version 2.6.
 
 .sp
-The LDAP server against which the \fBmongoldap\fP executes LDAP operations
-against to authenticate users or determine what actions a user is authorized
-to perform on a given database. If the LDAP server specified has any
-replicated instances, you may specify the host and port of each replicated
-server in a comma\-delimited list.
+Specifies the \fB\&.pem\fP file that contains the root certificate chain
+from the Certificate Authority. Specify the file name of the
+\fB\&.pem\fP file using relative or absolute paths.
 .sp
-If your LDAP infrastrucure partitions the LDAP directory over multiple LDAP
-servers, specify \fIone\fP LDAP server any of its replicated instances to
-\fI\%\-\-ldapServers\fP\&. MongoDB supports following LDAP referrals as defined in \fI\%RFC 4511
-4.1.10\fP\&. Do not use \fI\%\-\-ldapServers\fP
-for listing every LDAP server in your infrastructure.
+Starting in version 3.4, if \fB\-\-tlsCAFile\fP/\fBnet.tls.CAFile\fP (or
+their aliases \fB\-\-sslCAFile\fP/\fBnet.ssl.CAFile\fP) is not specified
+and you are not using x.509 authentication, the system\-wide CA
+certificate store will be used when connecting to an TLS/SSL\-enabled
+server.
 .sp
-This setting can be configured on a running \fBmongoldap\fP using
-\fBsetParameter\fP\&.
+To use x.509 authentication, \fB\-\-tlsCAFile\fP or \fBnet.tls.CAFile\fP
+must be specified unless using \fB\-\-tlsCertificateSelector\fP or
+\fB\-\-net.tls.certificateSelector\fP\&. Or if using the \fBssl\fP aliases,
+\fB\-\-sslCAFile\fP or \fBnet.ssl.CAFile\fP must be specified unless using
+\fB\-\-sslCertificateSelector\fP or \fBnet.ssl.certificateSelector\fP\&.
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+\fBVersion 3.2 and earlier:\fP For TLS/SSL connections (\fB\-\-ssl\fP) to
+\fBmongod\fP and \fBmongos\fP, if the \fBmongoimport\fP runs without the
+\fI\%\-\-sslCAFile\fP, \fBmongoimport\fP will not attempt
+to validate the server certificates. This creates a vulnerability
+to expired \fBmongod\fP and \fBmongos\fP certificates as
+well as to foreign processes posing as valid \fBmongod\fP or
+\fBmongos\fP instances. Ensure that you \fIalways\fP specify the
+CA file to validate the server certificates in cases where
+intrusion is a possibility.
+.UNINDENT
+.UNINDENT
 .sp
-If unset, \fBmongoldap\fP cannot use LDAP authentication or authorization\&.
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapQueryUser <string>
-New in version 3.4: Available in MongoDB Enterprise only.
+.B \-\-sslPEMKeyFile=<filename>
+New in version 2.6.
 
 .sp
-The identity with which \fBmongoldap\fP binds as, when connecting to or
-performing queries on an LDAP server.
+Specifies the \fB\&.pem\fP file that contains both the TLS/SSL certificate
+and key. Specify the file name of the \fB\&.pem\fP file using relative
+or absolute paths.
 .sp
-Only required if any of the following are true:
-.INDENT 7.0
-.IP \(bu 2
-Using LDAP authorization\&.
-.IP \(bu 2
-Using an LDAP query for \fI\%username transformation\fP\&.
-.IP \(bu 2
-The LDAP server disallows anonymous binds
+This option is required when using the \fI\%\-\-ssl\fP option to connect
+to a \fBmongod\fP or \fBmongos\fP that has
+\fBCAFile\fP enabled \fIwithout\fP
+\fBallowConnectionsWithoutCertificates\fP\&.
+.sp
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-sslPEMKeyPassword=<value>
+New in version 2.6.
+
 .sp
-You must use \fI\%\-\-ldapQueryUser\fP with \fI\%\-\-ldapQueryPassword\fP\&.
+Specifies the password to de\-crypt the certificate\-key file (i.e.
+\fI\%\-\-sslPEMKeyFile\fP). Use the \fI\%\-\-sslPEMKeyPassword\fP option only if the
+certificate\-key file is encrypted. In all cases, the \fBmongoimport\fP will
+redact the password from all logging and reporting output.
 .sp
-If unset, \fBmongoldap\fP will not attempt to bind to the LDAP server.
+If the private key in the PEM file is encrypted and you do not specify
+the \fI\%\-\-sslPEMKeyPassword\fP option, the \fBmongoimport\fP will prompt for a passphrase. See
+ssl\-certificate\-password\&.
 .sp
-This setting can be configured on a running \fBmongoldap\fP using
-\fBsetParameter\fP\&.
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-sslCRLFile=<filename>
+New in version 2.6.
+
 .sp
-\fBNOTE:\fP
+Specifies the \fB\&.pem\fP file that contains the Certificate Revocation
+List. Specify the file name of the \fB\&.pem\fP file using relative or
+absolute paths.
+.sp
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-sslAllowInvalidCertificates
+New in version 2.6.
+
+.sp
+Bypasses the validation checks for server certificates and allows
+the use of invalid certificates. When using the
+\fBallowInvalidCertificates\fP setting, MongoDB logs as a
+warning the use of the invalid certificate.
+.sp
+Starting in MongoDB 4.0, if you specify
+\fB\-\-sslAllowInvalidCertificates\fP or
+\fBnet.ssl.allowInvalidCertificates: true\fP (or in MongoDB 4.2, the
+alias \fB\-\-tlsAllowInvalidateCertificates\fP or
+\fBnet.tls.allowInvalidCertificates: true\fP) when using x.509
+authentication, an invalid certificate is only sufficient to
+establish a TLS/SSL connection but is \fIinsufficient\fP for
+authentication.
+.sp
+\fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
-Windows MongoDB deployments can use \fI\%\-\-ldapBindWithOSDefaults\fP
-instead of \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapQueryPassword\fP\&. You cannot specify
-both \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapBindWithOSDefaults\fP at the same time.
+Although available, avoid using the
+\fB\-\-sslAllowInvalidCertificates\fP option if possible. If the use of
+\fB\-\-sslAllowInvalidCertificates\fP is necessary, only use the option
+on systems where intrusion is not possible.
+.sp
+If the \fBmongo\fP shell (and other
+mongodb\-tools\-support\-ssl) runs with the
+\fB\-\-sslAllowInvalidCertificates\fP option, the
+\fBmongo\fP shell (and other
+mongodb\-tools\-support\-ssl) will not attempt to validate
+the server certificates. This creates a vulnerability to expired
+\fBmongod\fP and \fBmongos\fP certificates as
+well as to foreign processes posing as valid
+\fBmongod\fP or \fBmongos\fP instances. If you
+only need to disable the validation of the hostname in the
+TLS/SSL certificates, see \fB\-\-sslAllowInvalidHostnames\fP\&.
 .UNINDENT
 .UNINDENT
+.sp
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapQueryPassword <string>
-New in version 3.4: Available in MongoDB Enterprise only.
-.sp
-The password used to bind to an LDAP server when using
-\fI\%\-\-ldapQueryUser\fP\&. You must use \fI\%\-\-ldapQueryPassword\fP with
-\fI\%\-\-ldapQueryUser\fP\&.
+.B \-\-sslAllowInvalidHostnames
+New in version 3.0.
 
 .sp
-If unset, \fBmongoldap\fP will not attempt to bind to the LDAP server.
+Disables the validation of the hostnames in TLS/SSL certificates. Allows
+\fBmongoimport\fP to connect to MongoDB instances even if the hostname in their
+certificates do not match the specified hostname.
 .sp
-This setting can be configured on a running \fBmongoldap\fP using
-\fBsetParameter\fP\&.
+For more information about TLS/SSL and MongoDB, see
+/tutorial/configure\-ssl and
+/tutorial/configure\-ssl\-clients .
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-username=<username>, \-u=<username>
+Specifies a username with which to authenticate to a MongoDB database
+that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
+\fI\%\-\-authenticationDatabase\fP options.
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
 .INDENT 3.5
-Windows MongoDB deployments can use \fI\%\-\-ldapBindWithOSDefaults\fP
-instead of \fI\%\-\-ldapQueryPassword\fP and \fI\%\-\-ldapQueryPassword\fP\&. You cannot specify
-both \fI\%\-\-ldapQueryPassword\fP and \fI\%\-\-ldapBindWithOSDefaults\fP at the same time.
+You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapBindWithOSDefaults <bool>
-\fIDefault\fP: False
-.sp
-New in version 3.4: Available in MongoDB Enterprise for the Windows platform only.
+.B \-\-password=<password>, \-p=<password>
+Specifies a password with which to authenticate to a MongoDB database
+that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
+\fI\%\-\-authenticationDatabase\fP options.
+.sp
+Changed in version 3.0.2: To prompt the user
+for the password, pass the \fI\%\-\-username\fP option without
+\fI\%\-\-password\fP or specify an empty string as the \fI\%\-\-password\fP value,
+as in \fB\-\-password ""\fP .
 
 .sp
-Allows \fBmongoldap\fP to authenticate, or bind, using your Windows login
-credentials when connecting to the LDAP server.
-.sp
-Only required if:
+\fBNOTE:\fP
 .INDENT 7.0
-.IP \(bu 2
-Using LDAP authorization\&.
-.IP \(bu 2
-Using an LDAP query for \fI\%username transformation\fP\&.
-.IP \(bu 2
-The LDAP server disallows anonymous binds
+.INDENT 3.5
+You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
+.UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-authenticationDatabase=<dbname>
+Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
+See user\-authentication\-database\&.
 .sp
-Use \fI\%\-\-ldapBindWithOSDefaults\fP to replace \fI\%\-\-ldapQueryUser\fP and
-\fI\%\-\-ldapQueryPassword\fP\&.
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+You cannot specify both \fI\%\-\-authenticationDatabase\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapBindMethod <string>
-\fIDefault\fP: simple
+.B \-\-authenticationMechanism=<name>
+\fIDefault\fP: SCRAM\-SHA\-1
+.sp
+Specifies the authentication mechanism the \fBmongoimport\fP instance uses to
+authenticate to the \fBmongod\fP or \fBmongos\fP\&.
+.sp
+Changed in version 4.0: MongoDB removes support for the deprecated MongoDB
+Challenge\-Response (\fBMONGODB\-CR\fP) authentication mechanism.
 .sp
-New in version 3.4: Available in MongoDB Enterprise only.
+MongoDB adds support for SCRAM mechanism using the SHA\-256 hash
+function (\fBSCRAM\-SHA\-256\fP).
 
+.TS
+center;
+|l|l|.
+_
+T{
+Value
+T}	T{
+Description
+T}
+_
+T{
+SCRAM\-SHA\-1
+T}	T{
+\fI\%RFC 5802\fP standard
+Salted Challenge Response Authentication Mechanism using the SHA\-1
+hash function.
+T}
+_
+T{
+SCRAM\-SHA\-256
+T}	T{
+\fI\%RFC 7677\fP standard
+Salted Challenge Response Authentication Mechanism using the SHA\-256
+hash function.
+.sp
+Requires featureCompatibilityVersion set to \fB4.0\fP\&.
 .sp
-The method \fBmongoldap\fP uses to authenticate to an LDAP server.
-Use with \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapQueryPassword\fP to
-connect to the LDAP server.
+New in version 4.0.
+T}
+_
+T{
+MONGODB\-X509
+T}	T{
+MongoDB TLS/SSL certificate authentication.
+T}
+_
+T{
+GSSAPI (Kerberos)
+T}	T{
+External authentication using Kerberos. This mechanism is
+available only in \fI\%MongoDB Enterprise\fP\&.
+T}
+_
+T{
+PLAIN (LDAP SASL)
+T}	T{
+External authentication using LDAP. You can also use \fBPLAIN\fP
+for authenticating in\-database users. \fBPLAIN\fP transmits
+passwords in plain text. This mechanism is available only in
+\fI\%MongoDB Enterprise\fP\&.
+T}
+_
+.TE
 .sp
-\fI\%\-\-ldapBindMethod\fP supports the following values:
+\fBNOTE:\fP
 .INDENT 7.0
-.IP \(bu 2
-\fBsimple\fP \- \fBmongoldap\fP uses simple authentication.
-.IP \(bu 2
-\fBsasl\fP \- \fBmongoldap\fP uses SASL protocol for authentication
+.INDENT 3.5
+You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
 .UNINDENT
-.sp
-If you specify \fBsasl\fP, you can configure the available SASL mechanisms
-using \fI\%\-\-ldapBindSASLMechanisms\fP\&. \fBmongoldap\fP defaults to
-using \fBDIGEST\-MD5\fP mechanism.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapBindSASLMechanisms <string>
-\fIDefault\fP: DIGEST\-MD5
-.sp
-New in version 3.4: Available in MongoDB Enterprise only.
+.B \-\-gssapiServiceName=<serviceName>
+New in version 2.6.
 
 .sp
-A comma\-separated list of SASL mechanisms \fBmongoldap\fP can
-use when authenticating to the LDAP server. The \fBmongoldap\fP and the
-LDAP server must agree on at least one mechanism. The \fBmongoldap\fP
-dynamically loads any SASL mechanism libraries installed on the host
-machine at runtime.
-.sp
-Install and configure the appropriate libraries for the selected
-SASL mechanism(s) on both the \fBmongoldap\fP host and the remote
-LDAP server host. Your operating system may include certain SASL
-libraries by default. Defer to the documentation associated with each
-SASL mechanism for guidance on installation and configuration.
-.sp
-If using the \fBGSSAPI\fP SASL mechanism for use with
-security\-kerberos, verify the following for the
-\fBmongoldap\fP host machine:
-.INDENT 7.0
-.TP
-.B \fBLinux\fP
-.INDENT 7.0
-.IP \(bu 2
-The \fBKRB5_CLIENT_KTNAME\fP environment
-variable resolves to the name of the client keytab\-files
-for the host machine. For more on Kerberos environment
-variables, please defer to the
-\fI\%Kerberos documentation\fP\&.
-.IP \(bu 2
-The client keytab includes a
-kerberos\-user\-principal for the \fBmongoldap\fP to use when
-connecting to the LDAP server and execute LDAP queries.
+Specify the name of the service using GSSAPI/Kerberos\&. Only required if the service does not use the
+default name of \fBmongodb\fP\&.
+.sp
+This option is available only in MongoDB Enterprise.
 .UNINDENT
+.INDENT 0.0
 .TP
-.B \fBWindows\fP
-If connecting to an Active Directory server, the Windows
-Kerberos configuration automatically generates a
-\fI\%Ticket\-Granting\-Ticket\fP
-when the user logs onto the system. Set \fI\%\-\-ldapBindWithOSDefaults\fP to
-\fBtrue\fP to allow \fBmongoldap\fP to use the generated credentials when
-connecting to the Active Directory server and execute queries.
-.UNINDENT
+.B \-\-gssapiHostName=<hostname>
+New in version 2.6.
+
 .sp
-Set \fI\%\-\-ldapBindMethod\fP to \fBsasl\fP to use this option.
+Specify the hostname of a service using GSSAPI/Kerberos\&. \fIOnly\fP required if the hostname of a machine does
+not match the hostname resolved by DNS.
+.sp
+This option is available only in MongoDB Enterprise.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-db=<database>, \-d=<database>
+Specifies the name of the database on which to run the \fBmongoimport\fP\&.
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
 .INDENT 3.5
-For a complete list of SASL mechanisms see the
-\fI\%IANA listing\fP\&.
-Defer to the documentation for your LDAP or Active Directory
-service for identifying the SASL mechanisms compatible with the
-service.
+You cannot specify both \fI\%\-\-db\fP and \fI\%\-\-uri\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-collection=<collection>, \-c=<collection>
+Specifies the collection to import.
 .sp
-MongoDB is not a source of SASL mechanism libraries, nor
-is the MongoDB documentation a definitive source for
-installing or configuring any given SASL mechanism. For
-documentation and support, defer to the SASL mechanism
-library vendor or owner.
+New in version 2.6: If you do not specify \fI\%\-\-collection\fP,
+\fI\%mongoimport\fP takes the collection name from the input
+filename. MongoDB omits the extension of the file from the
+collection name, if the input file has an extension.
+
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-fields=<field1[,field2]>, \-f=<field1[,field2]>
+Specify a comma separated list of field names when importing csv
+or tsv files that do not have field names in the first (i.e.
+header) line of the file.
 .sp
-For more information on SASL, defer to the following resources:
+To also specify the field type as well as the field name, use
+\fI\%\-\-fields\fP with \fI\%\-\-columnsHaveTypes\fP\&.
+.sp
+If you attempt to include \fI\%\-\-fields\fP when importing JSON data,
+\fBmongoimport\fP will return an error. \fI\%\-\-fields\fP is only for csv
+or tsv imports.
+.UNINDENT
 .INDENT 0.0
-.IP \(bu 2
-For Linux, please see the \fI\%Cyrus SASL documentation\fP\&.
-.IP \(bu 2
-For Windows, please see the \fI\%Windows SASL documentation\fP\&.
+.TP
+.B \-\-fieldFile=<filename>
+As an alternative to \fI\%\-\-fields\fP, the \fI\%\-\-fieldFile\fP
+option allows you to specify a file that holds a list of field names if
+your csv or tsv file does not include field names in the
+first line of the file (i.e. header). Place one field per line.
+.sp
+To also specify the field type as well as the field name, use
+\fI\%\-\-fieldFile\fP with \fI\%\-\-columnsHaveTypes\fP\&.
+.sp
+If you attempt to include \fI\%\-\-fieldFile\fP when importing JSON data,
+\fBmongoimport\fP will return an error. \fI\%\-\-fieldFile\fP is only for csv
+or tsv imports.
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ignoreBlanks
+Ignores empty fields in csv and tsv exports. If not
+specified, \fI\%mongoimport\fP creates fields without values in
+imported documents.
+.sp
+If you attempt to include \fI\%\-\-ignoreBlanks\fP when importing JSON data,
+\fBmongoimport\fP will return an error. \fI\%\-\-ignoreBlanks\fP is only for csv
+or tsv imports.
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-type=<json|csv|tsv>
+Specifies the file type to import. The default format is JSON,
+but it\(aqs possible to import csv and tsv files.
+.sp
+The \fBcsv\fP parser accepts that data that complies with RFC
+\fI\%RFC 4180\fP\&. As a result, backslashes are \fInot\fP a valid escape
+character. If you use double\-quotes to enclose fields in the CSV
+data, you must escape internal double\-quote marks by prepending
+another double\-quote.
 .UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-file=<filename>
+Specifies the location and name of a file containing the data to import.
+If you do not specify a file, \fI\%mongoimport\fP reads data from
+standard input (e.g. "stdin").
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapTransportSecurity <string>
-\fIDefault\fP: tls
+.B \-\-drop
+Modifies the import process so that the target instance drops
+the collection before importing the data from the input.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-headerline
+If using \fI\%\-\-type csv\fP or \fI\%\-\-type
+tsv\fP, uses the first line as field names.
+Otherwise, \fI\%mongoimport\fP will import the first line as a
+distinct document.
+.sp
+If you attempt to include \fI\%\-\-headerline\fP when importing JSON data,
+\fBmongoimport\fP will return an error. \fI\%\-\-headerline\fP is only for csv
+or tsv imports.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-mode=<insert|upsert|merge>
+\fIDefault\fP: insert
 .sp
-New in version 3.4: Available in MongoDB Enterprise only.
+New in version 3.4.
 
 .sp
-By default, \fBmongoldap\fP creates a TLS/SSL secured connection to the LDAP
-server.
+Specifies how the import process should handle existing documents
+in the database that match documents in the import file.
 .sp
-For Linux deployments, you must configure the appropriate TLS Options in
-\fB/etc/openldap/ldap.conf\fP file. Your operating system\(aqs package manager
-creates this file as part of the MongoDB Enterprise installation, via the
-\fBlibldap\fP dependency. See the documentation for \fBTLS Options\fP in the
-\fI\%ldap.conf OpenLDAP documentation\fP
-for more complete instructions.
+By default, \fBmongoimport\fP uses the \fB_id\fP field to match documents in
+the collection with documents in the import file.
+To specify the fields against which to match existing
+documents for the \fBupsert\fP and \fBmerge\fP modes,
+use \fI\%\-\-upsertFields\fP\&.
+.TS
+center;
+|l|l|.
+_
+T{
+Value
+T}	T{
+Description
+T}
+_
+T{
+\fBinsert\fP
+T}	T{
+Insert the documents in the import file. \fBmongoimport\fP will log
+an error if you attempt to import a document that contains a
+duplicate value for a field with a unique index, such as \fB_id\fP\&.
+T}
+_
+T{
+\fBupsert\fP
+T}	T{
+Replace existing documents in the database with matching
+documents from the
+import file. \fBmongoimport\fP will insert all other
+documents. \fI\%Replace Matching Documents during Import\fP describes how to
+use \fI\%\-\-mode\fP \fBupsert\fP\&.
+T}
+_
+T{
+\fBmerge\fP
+T}	T{
+Merge existing documents that match a document in the import file with
+the new document. \fBmongoimport\fP will insert all other documents.
+\fI\%Merge Matching Documents during Import\fP describes how to use \fI\%\-\-mode\fP
+\fBmerge\fP\&.
+T}
+_
+.TE
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-upsertFields=<field1[,field2]>
+Specifies a list of fields for the query portion of the
+upsert\&.
+Use this option if the \fB_id\fP fields in the
+existing documents don\(aqt match the field in the document, but
+another field or field combination can uniquely identify
+documents as a basis for performing upsert operations.
+.sp
+Changed in version 3.4: Modifies the import process to update existing objects in the
+database if they match based on the specified fields, while
+inserting all other objects. You do not need to use \fI\%\-\-mode
+upsert\fP with \fI\%\-\-upsertFields\fP\&.
+.sp
+If you do not specify a field, \fI\%\-\-upsertFields\fP will upsert on the basis of
+the \fB_id\fP field.
+
 .sp
-For Windows deployment, you must add the LDAP server CA certificates to the
-Windows certificate management tool. The exact name and functionality of the
-tool may vary depending on operating system version. Please see the
-documentation for your version of Windows for more information on
-certificate management.
+To ensure adequate performance, indexes should exist for this
+field or fields.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-stopOnError
+Forces \fBmongoimport\fP to halt the insert operation at the
+first error rather than continuing the operation despite errors.
 .sp
-Set \fI\%\-\-ldapTransportSecurity\fP to \fBnone\fP to disable TLS/SSL between \fBmongoldap\fP and the LDAP
-server.
+Starting in version 4.2, \fI\%mongoimport\fP, by default,
+continues when it encounters duplicate key and document
+validation errors.  To ensure that the program stops on these errors, specify \fI\%\-\-stopOnError\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-jsonArray
+Accepts the import of data expressed with multiple MongoDB documents
+within a single JSON array. Limited to
+imports of 16 MB or smaller.
 .sp
-\fBWARNING:\fP
+Use \fI\%\-\-jsonArray\fP in conjunction with \fBmongoexport \-\-jsonArray\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-legacy
+Indicates that the import data is in Extended JSON v1 format instead of the default
+Extended JSON v2 format\&.
 .INDENT 7.0
 .INDENT 3.5
-Setting \fI\%\-\-ldapTransportSecurity\fP to \fBnone\fP transmits plaintext information and possibly
-credentials between \fBmongoldap\fP and the LDAP server.
+.SH TIP
+.sp
+In general, the versions of \fBmongoexport\fP and
+\fI\%mongoimport\fP should match. That is, to import
+data created from \fBmongoexport\fP, you should use
+the corresponding version of \fI\%mongoimport\fP\&.
 .UNINDENT
 .UNINDENT
+.sp
+For example, if the import data is in v1 format:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{"_id":1.0,"myregfield":{"$regex":"foo","$options":"i"}}
+.ft P
+.fi
+.UNINDENT
 .UNINDENT
-.INDENT 0.0
-.TP
-.B \-\-ldapTimeoutMS <long>
-\fIDefault\fP: 10000
 .sp
-New in version 3.4: Available in MongoDB Enterprise only.
-
+Import without the \fI\%\-\-legacy\fP option results in
+the following document in the collection:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{ "_id" : 1, "myregfield" : { "$regex" : "foo", "$options" : "i" } }
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-The amount of time in milliseconds \fBmongoldap\fP should wait for an LDAP server
-to respond to a request.
+Import with the \fI\%\-\-legacy\fP results in
+the following document in the collection:
+.INDENT 7.0
+.INDENT 3.5
 .sp
-Increasing the value of \fI\%\-\-ldapTimeoutMS\fP may prevent connection failure between the
-MongoDB server and the LDAP server, if the source of the failure is a
-connection timeout. Decreasing the value of \fI\%\-\-ldapTimeoutMS\fP reduces the time
-MongoDB waits for a response from the LDAP server.
+.nf
+.ft C
+{ "_id" : 1, "myregfield" : { "$regularExpression" : { "pattern" : "foo", "options" : "i" } } }
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-This setting can be configured on a running \fBmongoldap\fP using
-\fBsetParameter\fP\&.
+New in version 4.2.
+
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-ldapUserToDNMapping <string>
-New in version 3.4: Available in MongoDB Enterprise only.
-
+.B \-\-maintainInsertionOrder
+\fIDefault\fP: False
 .sp
-Maps the username provided to \fBmongoldap\fP for authentication to a LDAP
-Distinguished Name (DN). You may need to use \fI\%\-\-ldapUserToDNMapping\fP to transform a
-username into an LDAP DN in the following scenarios:
+If specified,
 .INDENT 7.0
 .IP \(bu 2
-Performing LDAP authentication with simple LDAP binding, where users
-authenticate to MongoDB with usernames that are not full LDAP DNs.
-.IP \(bu 2
-Using an \fBLDAP authorization query template\fP that requires a DN.
+Starting in version 4.2, \fBmongoimport\fP inserts the
+documents in the order of their appearance in the input source. That
+is, both the bulk write batch order and document order within the
+batches are maintained.
 .IP \(bu 2
-Transforming the usernames of clients authenticating to Mongo DB using
-different authentication mechanisms (e.g. x.509, kerberos) to a full LDAP
-DN for authorization.
+In earlier versions, only the batch order is maintained; document
+order within batches are not maintained.
 .UNINDENT
 .sp
-\fI\%\-\-ldapUserToDNMapping\fP expects a quote\-enclosed JSON\-string representing an ordered array
-of documents. Each document contains a regular expression \fBmatch\fP and
-either a \fBsubstitution\fP or \fBldapQuery\fP template used for transforming the
-incoming username.
+Starting in MongoDB 4.2, specifying
+\fI\%\-\-maintainInsertionOrder\fP also enables \fI\%\-\-stopOnError\fP and sets \fI\%numInsertionWorkers\fP to 1.
 .sp
-Each document in the array has the following form:
+If unspecified, \fBmongoimport\fP may perform the insertions in an
+arbitrary order.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-numInsertionWorkers=<int>
+\fIDefault\fP: 1
+.sp
+New in version 3.0.0.
+
+.sp
+Specifies the number of insertion workers to run concurrently.
+.sp
+For large imports, increasing the number of insertion workers
+may increase the speed of the import.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-writeConcern=<document>
+\fIDefault\fP: majority
+.sp
+Specifies the write concern for each write operation that \fBmongoimport\fP
+performs.
+.sp
+Specify the write concern as a document with w options:
 .INDENT 7.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-{
-  match: "<regex>"
-  substitution: "<LDAP DN>" | ldapQuery: "<LDAP Query>"
-}
+\-\-writeConcern "{w:\(aqmajority\(aq}"
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+If the write concern is also included in the \fI\%\-\-uri
+connection string\fP, the command\-line
+\fI\%\-\-writeConcern\fP overrides the write concern specified in
+the URI string.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-bypassDocumentValidation
+Enables \fBmongoimport\fP to bypass document validation
+during the operation. This lets you insert documents that do not
+meet the validation requirements.
+.sp
+New in version 3.2.1.
+
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-columnsHaveTypes
+New in version 3.4.
+
+.sp
+Instructs \fBmongoimport\fP that the
+field list specified in \fI\%\-\-fields\fP, \fI\%\-\-fieldFile\fP,
+or \fI\%\-\-headerline\fP specifies the types of each field.
+.sp
+Field names must be in the form of \fB<colName>.<type>(<arg>)\fP\&. You
+must backslash\-escape the following characters if you wish to include
+them in an argument: \fB(\fP, \fB)\fP, and \fB\e\fP\&.
 .TS
 center;
 |l|l|l|.
 _
 T{
-Field
+\fBtype\fP
 T}	T{
-Description
+Supported Arguments
 T}	T{
-Example
+Example Header Field
 T}
 _
 T{
-\fBmatch\fP
+\fBauto()\fP
 T}	T{
-An ECMAScript\-formatted regular expression (regex) to match against a
-provided username. Each parenthesis\-enclosed section represents a
-regex capture group used by \fBsubstitution\fP or \fBldapQuery\fP\&.
+None.
 T}	T{
-\fB"(.+)ENGINEERING"\fP
-\fB"(.+)DBA"\fP
+\fBmisc.auto()\fP
 T}
 _
 T{
-\fBsubstitution\fP
+\fBbinary(<arg>)\fP
+T}	T{
+.INDENT 7.0
+.IP \(bu 2
+\fBbase32\fP (\fI\%RFC4648\fP encoding schema)
+.IP \(bu 2
+\fBbase64\fP (\fI\%RFC4648\fP encoding schema)
+.IP \(bu 2
+\fBhex\fP
+.UNINDENT
 T}	T{
-An LDAP distinguished name (DN) formatting template that converts the
-authentication name matched by the \fBmatch\fP regex into a LDAP DN.
-Each curly bracket\-enclosed numeric value is replaced by the
-corresponding \fI\%regex capture group\fP extracted
-from the authentication username via the \fBmatch\fP regex.
+\fBuser thumbnail.binary(base64)\fP
+T}
+_
+T{
+\fBboolean()\fP
+T}	T{
+None.
+T}	T{
+\fBverified.boolean()\fP
+T}
+_
+T{
+\fBdate(<arg>)\fP
+T}	T{
+Alias for \fBdate_go(<arg>)\fP\&. \fI\%Go Language time.Parse format\fP\&.
+T}	T{
+\fBcreated.date(2006\-01\-02 15:04:05)\fP
+T}
+_
+T{
+\fBdate_go(<arg>)\fP
+T}	T{
+\fI\%Go Language time.Parse format\fP
+T}	T{
+\fBcreated.date_go(2006\-01\-02 15:04:05)\fP
+T}
+_
+T{
+\fBdate_ms(<arg>)\fP
+T}	T{
+\fI\%Microsoft SQL Server FORMAT format\fP
+T}	T{
+\fBcreated.date_ms(yyyy\-MM\-dd H:mm:ss)\fP
+T}
+_
+T{
+\fBdate_oracle(<arg>)\fP
+T}	T{
+\fI\%Oracle Database TO_DATE format\fP\&.
+T}	T{
+\fBcreated.date_oracle(YYYY\-MM\-DD HH24:MI:SS)\fP
+T}
+_
+T{
+\fBdecimal()\fP
+T}	T{
+None
+T}	T{
+\fBprice.decimal()\fP
+T}
+_
+T{
+\fBdouble()\fP
+T}	T{
+None.
+T}	T{
+\fBrevenue.double()\fP
+T}
+_
+T{
+\fBint32()\fP
+T}	T{
+None.
+T}	T{
+\fBfollowerCount.int32()\fP
+T}
+_
+T{
+\fBint64()\fP
+T}	T{
+None.
+T}	T{
+\fBbigNumber.int64()\fP
+T}
+_
+T{
+\fBstring()\fP
+T}	T{
+None.
+T}	T{
+\fBzipcode.string()\fP
+T}
+_
+.TE
+.sp
+See \fI\%Import CSV with Specified Field Types\fP for sample usage.
+.sp
+If you attempt to include \fI\%\-\-columnsHaveTypes\fP when importing JSON data,
+\fBmongoimport\fP will return an error. \fI\%\-\-columnsHaveTypes\fP is only for csv
+or tsv imports.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-parseGrace=<grace>
+\fIDefault\fP: stop
+.sp
+New in version 3.4.
+
 .sp
-The result of the substitution must be an \fI\%RFC4514\fP escaped string.
+Specifies how \fBmongoimport\fP handles type coercion failures when importing
+CSV or TSV files with \fI\%\-\-columnsHaveTypes\fP\&.
+.sp
+\fI\%\-\-parseGrace\fP has no effect when importing JSON documents.
+.TS
+center;
+|l|l|.
+_
+T{
+Value
 T}	T{
-\fB"cn={0},ou=engineering,
-dc=example,dc=com"\fP
+Description
 T}
 _
 T{
-\fBldapQuery\fP
-T}	T{
-A LDAP query formatting template that inserts the authentication
-name matched by the \fBmatch\fP regex into an LDAP query URI encoded
-respecting RFC4515 and RFC4516. Each curly bracket\-enclosed numeric
-value is replaced by the corresponding \fI\%regex capture group\fP extracted
-from the authentication username via the \fBmatch\fP expression.
-\fBmongoldap\fP executes the query against the LDAP server to retrieve
-the LDAP DN for the authenticated user. \fBmongoldap\fP requires
-exactly one returned result for the transformation to be
-successful, or \fBmongoldap\fP skips this transformation.
-T}	T{
-\fB"ou=engineering,dc=example,
-dc=com??one?(user={0})"\fP
+\fBautoCast\fP
+T}	T{
+Assigns a type based on the value of the field.
+For example, if a field is defined as a \fBdouble\fP and the
+value for that field was \fB"foo"\fP, \fBmongoimport\fP would make
+that field value a string type.
+T}
+_
+T{
+\fBskipField\fP
+T}	T{
+For the row being imported, \fBmongoimport\fP does not include the
+field whose type does not match the expected type.
+T}
+_
+T{
+\fBskipRow\fP
+T}	T{
+\fBmongoimport\fP does not import rows containing a value whose
+type does not match the expected type.
+T}
+_
+T{
+\fBstop\fP
+T}	T{
+\fBmongoimport\fP returns an error that ends the import.
 T}
 _
 .TE
+.UNINDENT
+.SH EXAMPLES
+.SS Simple Import
 .sp
-\fBNOTE:\fP
-.INDENT 7.0
+\fI\%mongoimport\fP restores a database from a backup taken with
+\fBmongoexport\fP\&. Most of the arguments to \fBmongoexport\fP also
+exist for \fI\%mongoimport\fP\&.
+.sp
+In the following example, \fI\%mongoimport\fP imports
+the JSON data from the \fBcontacts.json\fP file into the collection
+\fBcontacts\fP in the \fBusers\fP database.
+.INDENT 0.0
 .INDENT 3.5
-An explanation of  \fI\%RFC4514\fP,
-\fI\%RFC4515\fP,
-\fI\%RFC4516\fP, or LDAP queries is out
-of scope for the MongoDB Documentation. Please review the RFC directly or
-use your preferred LDAP resource.
+.sp
+.nf
+.ft C
+mongoimport \-\-db=users \-\-collection=contacts \-\-file=contacts.json
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.SS Replace Matching Documents during Import
 .sp
-For each document in the array, you must use either \fBsubstitution\fP or
-\fBldapQuery\fP\&. You \fIcannot\fP specify both in the same document.
+Changed in version 3.4: In MongoDB 3.4, \fI\%\-\-mode upsert\fP replaces the
+deprecated \fB\-\-upsert\fP option.
+
 .sp
-When performing authentication or authorization, \fBmongoldap\fP steps through
-each document in the array in the given order, checking the authentication
-username against the \fBmatch\fP filter.  If a match is found,
-\fBmongoldap\fP applies the transformation and uses the output for
-authenticating the user. \fBmongoldap\fP does not check the remaining documents
-in the array.
+With \fI\%\-\-mode\fP \fBupsert\fP, \fI\%mongoimport\fP replaces
+existing documents in the database that match a document in the
+import file with the document from the import file.
+Documents that do not match an existing document in the database are
+inserted as usual. By default \fI\%mongoimport\fP matches documents
+based on the \fB_id\fP field. Use \fI\%\-\-upsertFields\fP to specify
+the fields to match against.
 .sp
-If the given document does not match the provided authentication name, or
-the transformation described by the document fails, \fBmongoldap\fP continues
-through the list of documents to find additional matches. If no matches are
-found in any document, \fBmongoldap\fP returns an error.
-.INDENT 7.0
+Consider the following document in the \fBpeople\fP collection in the
+\fBexample\fP database:
+.INDENT 0.0
 .INDENT 3.5
-.SH EXAMPLE
 .sp
-The following shows two transformation documents. The first
-document matches against any string ending in \fB@ENGINEERING\fP, placing
-anything preceeding the suffix into a regex capture group. The
-second document matches against any string ending in \fB@DBA\fP, placing
-anything preceeding the suffix into a regex capture group.
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "name" : "Crystal Duncan",
+   "region" : "United States",
+   "email" : "crystal@example.com"
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-\fBIMPORTANT:\fP
+The following document exists in a \fBpeople\-20160927.json\fP JSON file.
+The \fB_id\fP field of the JSON object matches the \fB_id\fP field of the
+document in the \fBpeople\fP collection.
 .INDENT 0.0
 .INDENT 3.5
-You must pass the array to \fI\%\-\-ldapUserToDNMapping\fP as a string.
+.sp
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "username" : "crystal",
+   "likes" : [ "running", "pandas", "software development" ]
+}
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.sp
+To import the \fBpeople\-20160927.json\fP file and replace documents in
+the database that match the documents in the import file, specify \fI\%\-\-mode\fP
+\fBupsert\fP, as in the following:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-"[
-   {
-      match: "(.+)@ENGINEERING.EXAMPLE.COM",
-      substitution: "cn={0},ou=engineering,dc=example,dc=com"
-   },
-   {
-      match: "(.+)@DBA.EXAMPLE.COM",
-      ldapQuery: "ou=dba,dc=example,dc=com??one?(user={0})"
-
-   }
-
-]"
+mongoimport \-c=people \-d=example \-\-mode=upsert \-\-file=people\-20160927.json
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-A user with username \fBalice@ENGINEERING.EXAMPLE.COM\fP matches the first
-document. The regex capture group \fB{0}\fP corresponds to the string
-\fBalice\fP\&. The resulting output is the DN
-\fB"cn=alice,ou=engineering,dc=example,dc=com"\fP\&.
+The document in the \fBpeople\fP collection would then contain only
+the fields from the imported document, as in the following:
+.INDENT 0.0
+.INDENT 3.5
 .sp
-A user with username \fBbob@DBA.EXAMPLE.COM\fP matches the second document.
-The regex capture group \fB{0}\fP corresponds to the string \fBbob\fP\&.  The
-resulting output is the LDAP query
-\fB"ou=dba,dc=example,dc=com??one?(user=bob)"\fP\&. \fBmongoldap\fP executes this
-query against the LDAP server, returning the result
-\fB"cn=bob,ou=dba,dc=example,dc=com"\fP\&.
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "username" : "crystal",
+   "likes" : [ "running", "pandas", "software development" ]
+}
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.SS Merge Matching Documents during Import
 .sp
-If \fI\%\-\-ldapUserToDNMapping\fP is unset, \fBmongoldap\fP applies no transformations to the username
-when attempting to authenticate or authorize a user against the LDAP server.
+New in version 3.4.
+
 .sp
-This setting can be configured on a running \fBmongoldap\fP using the
-\fBsetParameter\fP database command.
-.UNINDENT
+With \fI\%\-\-mode\fP \fBmerge\fP, \fI\%mongoimport\fP enables you to
+merge fields from a new record with an existing document in the
+database. Documents that do not match an existing document in the
+database are inserted as usual. By default \fI\%mongoimport\fP
+matches documents based on the \fB_id\fP field. Use
+\fI\%\-\-upsertFields\fP to specify the fields to match against.
+.sp
+The \fBpeople\fP collection in the \fBexample\fP database contains the
+following document:
 .INDENT 0.0
-.TP
-.B \-\-ldapAuthzQueryTemplate <string>
-New in version 3.4: Available in MongoDB Enterprise only.
-
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "name" : "Crystal Duncan",
+   "region" : "United States",
+   "email" : "crystal@example.com"
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-A relative LDAP query URL formatted conforming to \fI\%RFC4515\fP and \fI\%RFC4516\fP that \fBmongoldap\fP executes to obtain
-the LDAP groups to which the authenticated user belongs to. The query is
-relative to the host or hosts specified in \fI\%\-\-ldapServers\fP\&.
+The following document exists in a \fBpeople\-20160927.json\fP JSON file.
+The \fB_id\fP field of the JSON object matches the \fB_id\fP field of the
+document in the \fBpeople\fP collection.
+.INDENT 0.0
+.INDENT 3.5
 .sp
-Use the \fB{USER}\fP placeholder in the URL to substitute the authenticated
-username, or the transformed username if a \fI\%username mapping\fP is specified.
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "username" : "crystal",
+   "email": "crystal.duncan@example.com",
+   "likes" : [ "running", "pandas", "software development" ]
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-When constructing the query URL, ensure that the order of LDAP parameters
-respects RFC4516:
-.INDENT 7.0
+To import the \fBpeople\-20160927.json\fP file and merge documents from
+the import file with matching documents in the database, specify
+\fI\%\-\-mode\fP \fBmerge\fP, as in the following:
+.INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[ dn  [ ? [attributes] [ ? [scope] [ ? [filter] [ ? [Extensions] ] ] ] ] ]
+mongoimport \-c=people \-d=example \-\-mode=merge \-\-file=people\-20160927.json
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-If your query includes an attribute, \fBmongoldap\fP assumes that the query
-retrieves a the DNs which this entity is member of.
+The import operation combines the fields from the JSON file with the
+original document in the database,
+matching the documents based on the \fB_id\fP field.
+During the import process, \fI\%mongoimport\fP adds the new \fBusername\fP and
+\fBlikes\fP fields to the document and updates the \fBemail\fP field with
+the value from the imported document, as in the following:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+   "_id" : ObjectId("580100f4da893943d393e909"),
+   "name" : "Crystal Duncan",
+   "region" : "United States",
+   "email" : "crystal.duncan@example.com",
+   "username" : "crystal",
+   "likes" : [
+      "running",
+      "pandas",
+      "software development"
+   ]
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Import \fBJSON\fP to Remote Host Running with Authentication
 .sp
-If your query does not include an attribute, \fBmongoldap\fP assumes
-the query retrieves all entities which the user is member of.
+In the following example, \fI\%mongoimport\fP imports data from the
+file \fB/opt/backups/mdb1\-examplenet.json\fP into the \fBcontacts\fP collection
+within the database \fBmarketing\fP on a remote MongoDB
+database with authentication enabled.
 .sp
-For each LDAP DN returned by the query, \fBmongoldap\fP assigns the authorized
-user a corresponding role on the \fBadmin\fP database. If a role on the on the
-\fBadmin\fP database exactly matches the DN, \fBmongoldap\fP grants the user the
-roles and privileges assigned to that role. See the
-\fBdb.createRole()\fP method for more information on creating roles.
-.INDENT 7.0
+\fI\%mongoimport\fP connects to the \fBmongod\fP instance running on
+the host \fBmongodb1.example.net\fP over port \fB37017\fP\&. It authenticates with the
+username \fBuser\fP; the example omits the \fI\%\-\-password\fP
+option to have \fI\%mongoimport\fP prompt for the password:
+.INDENT 0.0
 .INDENT 3.5
-.SH EXAMPLE
 .sp
-This LDAP query returns any groups listed in the LDAP user object\(aqs
-\fBmemberOf\fP attribute.
+.nf
+.ft C
+mongoimport \-\-host=mongodb1.example.net \-\-port=37017 \-\-username=user \-\-collection=contacts \-\-db=marketing \-\-file=/opt/backups/mdb1\-examplenet.json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBCSV\fP Import
+.SS General CSV Import
+.sp
+In the following example, \fI\%mongoimport\fP imports the csv
+formatted data in the \fB/opt/backups/contacts.csv\fP file into the
+collection \fBcontacts\fP in the \fBusers\fP database on the MongoDB
+instance running on the localhost port numbered
+\fB27017\fP\&.
+.sp
+Specifying \fI\%\-\-headerline\fP instructs
+\fI\%mongoimport\fP to determine the name of the fields using the first
+line in the CSV file.
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-"{USER}?memberOf?base"
+mongoimport \-\-db=users \-\-collection=contacts \-\-type=csv \-\-headerline \-\-file=/opt/backups/contacts.csv
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Your LDAP configuration may not include the \fBmemberOf\fP attribute as part
-of the user schema, may possess a different attribute for reporting group
-membership, or may not track group membership through attributes.
-Configure your query with respect to your own unique LDAP configuration.
+\fI\%mongoimport\fP uses the input file name, without the
+extension, as the collection name if \fB\-c\fP or \fB\-\-collection\fP is
+unspecified. The following example is therefore equivalent:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoimport \-\-db=users \-\-type=csv \-\-headerline \-\-file=/opt/backups/contacts.csv
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.SS Import CSV with Specified Field Types
 .sp
-If unset, \fBmongoldap\fP cannot authorize users using LDAP.
+New in version 3.4.
+
 .sp
-This setting can be configured on a running \fBmongoldap\fP using the
-\fBsetParameter\fP database command.
+Starting in MongoDB 3.4, when you specify the field name, you can also
+specify the data type. To specify field names and type, include
+\fI\%\-\-columnsHaveTypes\fP with
+either: \fI\%\-\-fields\fP, \fI\%\-\-fieldFile\fP, or \fI\%\-\-headerline\fP\&.
 .sp
-\fBNOTE:\fP
-.INDENT 7.0
+Specify field names and data types in the form
+\fB<colName>.<type>(<arg>)\fP\&.
+.sp
+For example, a \fB/example/file.csv\fP file contains the following data:
+.INDENT 0.0
 .INDENT 3.5
-An explanation of \fI\%RFC4515\fP,
-\fI\%RFC4516\fP or LDAP queries is out
-of scope for the MongoDB Documentation. Please review the RFC directly or
-use your preferred LDAP resource.
+.sp
+.nf
+.ft C
+Katherine Gray, 1996\-02\-03, false, 1235, TG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2NpbmcgZWxpdCwgc2VkIGRvIGVpdXNtb2QgdGVtcG9yIGluY2lkaWR1bnQgdXQgbGFib3JlIGV0IGRvbG9yZSBtYWduYSBhbGlxdWEuIFV0IGVuaW0gYWQgbWluaW0gdmVuaWFtLCBxdWlzIG5vc3RydWQgZXhlcmNpdGF0aW9uIHVsbGFtY28gbGFib3JpcyBuaXNpIHV0IGFsaXF1aXAgZXggZWEgY29tbW9kbyBjb25zZXF1YXQuIER1aXMgYXV0ZSBpcnVyZSBkb2xvciBpbiByZXByZWhlbmRlcml0IGluIHZvbHVwdGF0ZSB2ZWxpdCBlc3NlIGNpbGx1bSBkb2xvcmUgZXUgZnVnaWF0IG51bGxhIHBhcmlhdHVyLiBFeGNlcHRldXIgc2ludCBvY2NhZWNhdCBjdXBpZGF0YXQgbm9uIHByb2lkZW50LCBzdW50IGluIGN1bHBhIHF1aSBvZmZpY2lhIGRlc2VydW50IG1vbGxpdCBhbmltIGlkIGVzdCBsYWJvcnVtLg==
+Albert Gilbert, 1992\-04\-24, true, 13, Q3VwY2FrZSBpcHN1bSBkb2xvciBzaXQgYW1ldCB0b290c2llIHJvbGwgYm9uYm9uIHRvZmZlZS4gQ2FuZHkgY2FuZXMgcGllIGNyb2lzc2FudCBjaG9jb2xhdGUgYmFyIGxvbGxpcG9wIGJlYXIgY2xhdyBtYWNhcm9vbi4gU3dlZXQgcm9sbCBjdXBjYWtlIGNoZWVzZWNha2Ugc291ZmZsw6kgYnJvd25pZSBpY2UgY3JlYW0uIEp1anViZXMgY2FrZSBjdXBjYWtlIG1hY2Fyb29uIGRhbmlzaCBqZWxseS1vIHNvdWZmbMOpLiBDYWtlIGFwcGxlIHBpZSBnaW5nZXJicmVhZCBjaG9jb2xhdGUgc3VnYXIgcGx1bS4gU3dlZXQgY2hvY29sYXRlIGNha2UgY2hvY29sYXRlIGNha2UganVqdWJlcyB0aXJhbWlzdSBvYXQgY2FrZS4gU3dlZXQgc291ZmZsw6kgY2hvY29sYXRlLiBMaXF1b3JpY2UgY290dG9uIGNhbmR5IGNob2NvbGF0ZSBtYXJzaG1hbGxvdy4gSmVsbHkgY29va2llIGNha2UgamVsbHkgYm==
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.sp
+The following operation uses \fI\%mongoimport\fP with the
+\fI\%\-\-fields\fP and
+\fI\%\-\-columnsHaveTypes\fP option
+to specify both the field names and the BSON types of the imported CSV
+data.
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoimport \-\-db=users \-\-collection=contacts \-\-type=csv \e
+   \-\-columnsHaveTypes \e
+   \-\-fields="name.string(),birthdate.date(2006\-01\-02),contacted.boolean(),followerCount.int32(),thumbnail.binary(base64)" \e
+   \-\-file=/example/file.csv
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Ignore Blank Fields
+.sp
+Use the \fI\%\-\-ignoreBlanks\fP option
+to ignore blank fields. For CSV and TSV imports, this
+option provides the desired functionality in most cases because it avoids
+inserting fields with null values into your collection.
+.sp
+The following example imports the data from \fBdata.csv\fP, skipping
+any blank fields:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoimport \-\-db=users \-\-collection=contacts \-\-type=csv \-\-file=/example/data.csv \-\-ignoreBlanks
+.ft P
+.fi
+.UNINDENT
 .UNINDENT
 .SH AUTHOR
 MongoDB Documentation Project
diff --git a/debian/mongoldap.1 b/debian/mongoldap.1
new file mode 100644
index 00000000000..8426035b4a8
--- /dev/null
+++ b/debian/mongoldap.1
@@ -0,0 +1,790 @@
+.\" Man page generated from reStructuredText.
+.
+.TH "MONGOLDAP" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
+.SH NAME
+mongoldap \- MongoDB LDAP Configuration Testing Utility
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.SS On this page
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Synopsis\fP
+.IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
+\fI\%Usage\fP
+.IP \(bu 2
+\fI\%Options\fP
+.UNINDENT
+.sp
+New in version 3.4: MongoDB Enterprise
+
+.SH SYNOPSIS
+.sp
+Starting in version 3.4, MongoDB Enterprise provides
+\fI\%mongoldap\fP for testing MongoDB\(aqs LDAP configuration
+options against a running LDAP server or set
+of servers.
+.sp
+To validate the LDAP options in the configuration file, set the
+\fI\%mongoldap\fP \fI\%\-\-config\fP option to the configuration file\(aqs
+path.
+.sp
+To test the LDAP configuration options, you must specify a \fI\%\-\-user\fP
+and \fB\-\-password\fP\&. \fI\%mongoldap\fP simulates authentication to a
+MongoDB server running with the provided configuration options and credentials.
+.sp
+\fI\%mongoldap\fP returns a report that includes the success or failure of
+any step in the LDAP authentication or authorization procedure. Error messages
+include information on specific errors encountered and potential advice for
+resolving the error.
+.sp
+When configuring options related to LDAP authorization, \fI\%mongoldap\fP executes an LDAP query
+constructed using the provided configuration options and username, and returns
+a list of roles on the \fBadmin\fP database which the user is authorized for.
+.sp
+You can use this information when configuring LDAP authorization roles for user access control. For example, use
+\fI\%mongoldap\fP to ensure your configuration allows privileged users to
+gain the necessary roles to perform their expected tasks. Similarly, use
+\fI\%mongoldap\fP to ensure your configuration disallows non\-privileged
+users from gaining roles for accessing the MongoDB server, or performing
+unauthorized actions.
+.sp
+When configuring options related to LDAP authentication, use \fI\%mongoldap\fP to ensure that the authentication
+operation works as expected.
+.sp
+Run \fI\%mongoldap\fP from the system command line, not the \fBmongo\fP shell.
+.sp
+This document provides a complete overview of all command line options for
+\fI\%mongoldap\fP\&.
+.SH AVAILABILITY
+.sp
+The \fI\%mongoldap\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer for the Enterprise edition includes \fBmongoldap\fP as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
+.SH USAGE
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+A full description of LDAP or Active Directory is beyond the scope of
+this documentation.
+.UNINDENT
+.UNINDENT
+.sp
+Consider the following sample configuration file, designed to support
+LDAP authentication and authorization via Active Directory:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+security:
+   authorization: "enabled"
+   ldap:
+      servers: "activedirectory.example.net"
+      bind:
+         queryUser: "mongodbadmin@dba.example.com"
+         queryPassword: "secret123"
+      userToDNMapping:
+         \(aq[
+            {
+               match : "(.+)",
+               ldapQuery: "DC=example,DC=com??sub?(userPrincipalName={0})"
+            }
+         ]\(aq
+      authz:
+         queryTemplate: "DC=example,DC=com??sub?(&(objectClass=group)(member:1.2.840.113556.1.4.1941:={USER}))"
+setParameter:
+   authenticationMechanisms: "PLAIN"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You can use \fI\%mongoldap\fP to validate the configuration file, which
+returns a report of the procedure. You must specify a username and password
+for \fI\%mongoldap\fP\&.
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoldap \-\-config=<path\-to\-config> \-\-user="bob@dba.example.com" \-\-password="secret123"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If the provided credentials are valid, and the LDAP options in the
+configuration files are valid, the output might be as follows:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+Checking that an LDAP server has been specified...
+[OK] LDAP server found
+
+Connecting to LDAP server...
+[OK] Connected to LDAP server
+
+Parsing MongoDB to LDAP DN mappings..
+[OK] MongoDB to LDAP DN mappings appear to be valid
+
+Attempting to authenticate against the LDAP server...
+[OK] Successful authentication performed
+
+Checking if LDAP authorization has been enabled by configuration...
+[OK] LDAP authorization enabled
+
+Parsing LDAP query template..
+[OK] LDAP query configuration template appears valid
+
+Executing query against LDAP server...
+[OK] Successfully acquired the following roles:
+\&...
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-config=<filename>, \-f=<filename>
+Specifies a configuration file for runtime configuration options.
+The options are equivalent to the command\-line
+configuration options. See /reference/configuration\-options for
+more information.
+.sp
+\fBmongoldap\fP uses any configuration options related to security\-ldap
+or security\-ldap\-external for testing LDAP authentication or
+authorization.
+.sp
+Requires specifying \fI\%\-\-user\fP\&. May accept \fI\%\-\-password\fP for
+testing LDAP authentication.
+.sp
+Ensure the configuration file uses ASCII encoding. The \fBmongoldap\fP
+instance does not support configuration files with non\-ASCII encoding,
+including UTF\-8.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-user=<string>
+Username for \fBmongoldap\fP to use when attempting LDAP authentication or
+authorization.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-password=<string>
+Password of the \fI\%\-\-user\fP for
+\fBmongoldap\fP to use when attempting LDAP authentication. Not
+required for LDAP authorization.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapServers=<host1>:<port>,<host2>:<port>,...,<hostN>:<port>
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+The LDAP server against which the \fBmongoldap\fP authenticates users or
+determines what actions a user is authorized to perform on a given
+database. If the LDAP server specified has any replicated instances,
+you may specify the host and port of each replicated server in a
+comma\-delimited list.
+.sp
+If your LDAP infrastructure partitions the LDAP directory over multiple LDAP
+servers, specify \fIone\fP LDAP server or any of its replicated instances to
+\fI\%\-\-ldapServers\fP\&. MongoDB supports following LDAP referrals as defined in \fI\%RFC 4511
+4.1.10\fP\&. Do not use \fI\%\-\-ldapServers\fP
+for listing every LDAP server in your infrastructure.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using
+\fBsetParameter\fP\&.
+.sp
+If unset, \fBmongoldap\fP cannot use LDAP authentication or authorization\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapQueryUser=<string>
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+The identity with which \fBmongoldap\fP binds as, when connecting to or
+performing queries on an LDAP server.
+.sp
+Only required if any of the following are true:
+.INDENT 7.0
+.IP \(bu 2
+Using LDAP authorization\&.
+.IP \(bu 2
+Using an LDAP query for \fI\%username transformation\fP\&.
+.IP \(bu 2
+The LDAP server disallows anonymous binds
+.UNINDENT
+.sp
+You must use \fI\%\-\-ldapQueryUser\fP with \fI\%\-\-ldapQueryPassword\fP\&.
+.sp
+If unset, \fBmongoldap\fP will not attempt to bind to the LDAP server.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using
+\fBsetParameter\fP\&.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Windows MongoDB deployments can use \fI\%\-\-ldapBindWithOSDefaults\fP
+instead of \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapQueryPassword\fP\&. You cannot specify
+both \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapBindWithOSDefaults\fP at the same time.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapQueryPassword=<string>
+New in version 3.4: Available in MongoDB Enterprise only.
+.sp
+The password used to bind to an LDAP server when using
+\fI\%\-\-ldapQueryUser\fP\&. You must use \fI\%\-\-ldapQueryPassword\fP with
+\fI\%\-\-ldapQueryUser\fP\&.
+
+.sp
+If unset, \fBmongoldap\fP will not attempt to bind to the LDAP server.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using
+\fBsetParameter\fP\&.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Windows MongoDB deployments can use \fI\%\-\-ldapBindWithOSDefaults\fP
+instead of \fI\%\-\-ldapQueryPassword\fP and \fI\%\-\-ldapQueryPassword\fP\&. You cannot specify
+both \fI\%\-\-ldapQueryPassword\fP and \fI\%\-\-ldapBindWithOSDefaults\fP at the same time.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapBindWithOSDefaults=<bool>
+\fIDefault\fP: False
+.sp
+New in version 3.4: Available in MongoDB Enterprise for the Windows platform only.
+
+.sp
+Allows \fBmongoldap\fP to authenticate, or bind, using your Windows login
+credentials when connecting to the LDAP server.
+.sp
+Only required if:
+.INDENT 7.0
+.IP \(bu 2
+Using LDAP authorization\&.
+.IP \(bu 2
+Using an LDAP query for \fI\%username transformation\fP\&.
+.IP \(bu 2
+The LDAP server disallows anonymous binds
+.UNINDENT
+.sp
+Use \fI\%\-\-ldapBindWithOSDefaults\fP to replace \fI\%\-\-ldapQueryUser\fP and
+\fI\%\-\-ldapQueryPassword\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapBindMethod=<string>
+\fIDefault\fP: simple
+.sp
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+The method \fBmongoldap\fP uses to authenticate to an LDAP
+server. Use with \fI\%\-\-ldapQueryUser\fP and \fI\%\-\-ldapQueryPassword\fP to connect to the LDAP server.
+.sp
+\fI\%\-\-ldapBindMethod\fP supports
+the following values:
+.TS
+center;
+|l|l|.
+_
+T{
+Value
+T}	T{
+Description
+T}
+_
+T{
+\fBsimple\fP
+T}	T{
+\fBmongoldap\fP uses simple authentication.
+T}
+_
+T{
+\fBsasl\fP
+T}	T{
+\fBmongoldap\fP uses SASL protocol for authentication.
+T}
+_
+.TE
+.sp
+If you specify \fBsasl\fP, you can configure the available SASL mechanisms
+using \fI\%\-\-ldapBindSASLMechanisms\fP\&. \fBmongoldap\fP defaults to
+using \fBDIGEST\-MD5\fP mechanism.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapBindSASLMechanisms=<string>
+\fIDefault\fP: DIGEST\-MD5
+.sp
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+A comma\-separated list of SASL mechanisms \fBmongoldap\fP can
+use when authenticating to the LDAP server. The \fBmongoldap\fP and the
+LDAP server must agree on at least one mechanism. The \fBmongoldap\fP
+dynamically loads any SASL mechanism libraries installed on the host
+machine at runtime.
+.sp
+Install and configure the appropriate libraries for the selected
+SASL mechanism(s) on both the \fBmongoldap\fP host and the remote
+LDAP server host. Your operating system may include certain SASL
+libraries by default. Defer to the documentation associated with each
+SASL mechanism for guidance on installation and configuration.
+.sp
+If using the \fBGSSAPI\fP SASL mechanism for use with
+security\-kerberos, verify the following for the
+\fBmongoldap\fP host machine:
+.INDENT 7.0
+.TP
+.B \fBLinux\fP
+.INDENT 7.0
+.IP \(bu 2
+The \fBKRB5_CLIENT_KTNAME\fP environment
+variable resolves to the name of the client keytab\-files
+for the host machine. For more on Kerberos environment
+variables, please defer to the
+\fI\%Kerberos documentation\fP\&.
+.IP \(bu 2
+The client keytab includes a
+kerberos\-user\-principal for the \fBmongoldap\fP to use when
+connecting to the LDAP server and execute LDAP queries.
+.UNINDENT
+.TP
+.B \fBWindows\fP
+If connecting to an Active Directory server, the Windows
+Kerberos configuration automatically generates a
+\fI\%Ticket\-Granting\-Ticket\fP
+when the user logs onto the system. Set \fI\%\-\-ldapBindWithOSDefaults\fP to
+\fBtrue\fP to allow \fBmongoldap\fP to use the generated credentials when
+connecting to the Active Directory server and execute queries.
+.UNINDENT
+.sp
+Set \fI\%\-\-ldapBindMethod\fP to \fBsasl\fP to use this option.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+For a complete list of SASL mechanisms see the
+\fI\%IANA listing\fP\&.
+Defer to the documentation for your LDAP or Active Directory
+service for identifying the SASL mechanisms compatible with the
+service.
+.sp
+MongoDB is not a source of SASL mechanism libraries, nor
+is the MongoDB documentation a definitive source for
+installing or configuring any given SASL mechanism. For
+documentation and support, defer to the SASL mechanism
+library vendor or owner.
+.sp
+For more information on SASL, defer to the following resources:
+.INDENT 0.0
+.IP \(bu 2
+For Linux, please see the \fI\%Cyrus SASL documentation\fP\&.
+.IP \(bu 2
+For Windows, please see the \fI\%Windows SASL documentation\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapTransportSecurity=<string>
+\fIDefault\fP: tls
+.sp
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+By default, \fBmongoldap\fP creates a TLS/SSL secured connection to the LDAP
+server.
+.sp
+For Linux deployments, you must configure the appropriate TLS Options in
+\fB/etc/openldap/ldap.conf\fP file. Your operating system\(aqs package manager
+creates this file as part of the MongoDB Enterprise installation, via the
+\fBlibldap\fP dependency. See the documentation for \fBTLS Options\fP in the
+\fI\%ldap.conf OpenLDAP documentation\fP
+for more complete instructions.
+.sp
+For Windows deployment, you must add the LDAP server CA certificates to the
+Windows certificate management tool. The exact name and functionality of the
+tool may vary depending on operating system version. Please see the
+documentation for your version of Windows for more information on
+certificate management.
+.sp
+Set \fI\%\-\-ldapTransportSecurity\fP to \fBnone\fP to disable TLS/SSL between \fBmongoldap\fP and the LDAP
+server.
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+Setting \fI\%\-\-ldapTransportSecurity\fP to \fBnone\fP transmits plaintext information and possibly
+credentials between \fBmongoldap\fP and the LDAP server.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapTimeoutMS=<long>
+\fIDefault\fP: 10000
+.sp
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+The amount of time in milliseconds \fBmongoldap\fP should wait for an LDAP server
+to respond to a request.
+.sp
+Increasing the value of \fI\%\-\-ldapTimeoutMS\fP may prevent connection failure between the
+MongoDB server and the LDAP server, if the source of the failure is a
+connection timeout. Decreasing the value of \fI\%\-\-ldapTimeoutMS\fP reduces the time
+MongoDB waits for a response from the LDAP server.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using
+\fBsetParameter\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapUserToDNMapping=<string>
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+Maps the username provided to \fBmongoldap\fP for authentication to a LDAP
+Distinguished Name (DN). You may need to use \fI\%\-\-ldapUserToDNMapping\fP to transform a
+username into an LDAP DN in the following scenarios:
+.INDENT 7.0
+.IP \(bu 2
+Performing LDAP authentication with simple LDAP binding, where users
+authenticate to MongoDB with usernames that are not full LDAP DNs.
+.IP \(bu 2
+Using an \fBLDAP authorization query template\fP that requires a DN.
+.IP \(bu 2
+Transforming the usernames of clients authenticating to Mongo DB using
+different authentication mechanisms (e.g. x.509, kerberos) to a full LDAP
+DN for authorization.
+.UNINDENT
+.sp
+\fI\%\-\-ldapUserToDNMapping\fP expects a quote\-enclosed JSON\-string representing an ordered array
+of documents. Each document contains a regular expression \fBmatch\fP and
+either a \fBsubstitution\fP or \fBldapQuery\fP template used for transforming the
+incoming username.
+.sp
+Each document in the array has the following form:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  match: "<regex>"
+  substitution: "<LDAP DN>" | ldapQuery: "<LDAP Query>"
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.TS
+center;
+|l|l|l|.
+_
+T{
+Field
+T}	T{
+Description
+T}	T{
+Example
+T}
+_
+T{
+\fBmatch\fP
+T}	T{
+An ECMAScript\-formatted regular expression (regex) to match against a
+provided username. Each parenthesis\-enclosed section represents a
+regex capture group used by \fBsubstitution\fP or \fBldapQuery\fP\&.
+T}	T{
+\fB"(.+)ENGINEERING"\fP
+\fB"(.+)DBA"\fP
+T}
+_
+T{
+\fBsubstitution\fP
+T}	T{
+An LDAP distinguished name (DN) formatting template that converts the
+authentication name matched by the \fBmatch\fP regex into a LDAP DN.
+Each curly bracket\-enclosed numeric value is replaced by the
+corresponding \fI\%regex capture group\fP extracted
+from the authentication username via the \fBmatch\fP regex.
+.sp
+The result of the substitution must be an \fI\%RFC4514\fP escaped string.
+T}	T{
+\fB"cn={0},ou=engineering,
+dc=example,dc=com"\fP
+T}
+_
+T{
+\fBldapQuery\fP
+T}	T{
+A LDAP query formatting template that inserts the authentication
+name matched by the \fBmatch\fP regex into an LDAP query URI encoded
+respecting RFC4515 and RFC4516. Each curly bracket\-enclosed numeric
+value is replaced by the corresponding \fI\%regex capture group\fP extracted
+from the authentication username via the \fBmatch\fP expression.
+\fBmongoldap\fP executes the query against the LDAP server to retrieve
+the LDAP DN for the authenticated user. \fBmongoldap\fP requires
+exactly one returned result for the transformation to be
+successful, or \fBmongoldap\fP skips this transformation.
+T}	T{
+\fB"ou=engineering,dc=example,
+dc=com??one?(user={0})"\fP
+T}
+_
+.TE
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+An explanation of  \fI\%RFC4514\fP,
+\fI\%RFC4515\fP,
+\fI\%RFC4516\fP, or LDAP queries is out
+of scope for the MongoDB Documentation. Please review the RFC directly or
+use your preferred LDAP resource.
+.UNINDENT
+.UNINDENT
+.sp
+For each document in the array, you must use either \fBsubstitution\fP or
+\fBldapQuery\fP\&. You \fIcannot\fP specify both in the same document.
+.sp
+When performing authentication or authorization, \fBmongoldap\fP steps through
+each document in the array in the given order, checking the authentication
+username against the \fBmatch\fP filter.  If a match is found,
+\fBmongoldap\fP applies the transformation and uses the output for
+authenticating the user. \fBmongoldap\fP does not check the remaining documents
+in the array.
+.sp
+If the given document does not match the provided authentication name, or
+the transformation described by the document fails, \fBmongoldap\fP continues
+through the list of documents to find additional matches. If no matches are
+found in any document, \fBmongoldap\fP returns an error.
+.INDENT 7.0
+.INDENT 3.5
+.SH EXAMPLE
+.sp
+The following shows two transformation documents. The first
+document matches against any string ending in \fB@ENGINEERING\fP, placing
+anything preceeding the suffix into a regex capture group. The
+second document matches against any string ending in \fB@DBA\fP, placing
+anything preceeding the suffix into a regex capture group.
+.sp
+\fBIMPORTANT:\fP
+.INDENT 0.0
+.INDENT 3.5
+You must pass the array to \fI\%\-\-ldapUserToDNMapping\fP as a string.
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+"[
+   {
+      match: "(.+)@ENGINEERING.EXAMPLE.COM",
+      substitution: "cn={0},ou=engineering,dc=example,dc=com"
+   },
+   {
+      match: "(.+)@DBA.EXAMPLE.COM",
+      ldapQuery: "ou=dba,dc=example,dc=com??one?(user={0})"
+
+   }
+
+]"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+A user with username \fBalice@ENGINEERING.EXAMPLE.COM\fP matches the first
+document. The regex capture group \fB{0}\fP corresponds to the string
+\fBalice\fP\&. The resulting output is the DN
+\fB"cn=alice,ou=engineering,dc=example,dc=com"\fP\&.
+.sp
+A user with username \fBbob@DBA.EXAMPLE.COM\fP matches the second document.
+The regex capture group \fB{0}\fP corresponds to the string \fBbob\fP\&.  The
+resulting output is the LDAP query
+\fB"ou=dba,dc=example,dc=com??one?(user=bob)"\fP\&. \fBmongoldap\fP executes this
+query against the LDAP server, returning the result
+\fB"cn=bob,ou=dba,dc=example,dc=com"\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+If \fI\%\-\-ldapUserToDNMapping\fP is unset, \fBmongoldap\fP applies no transformations to the username
+when attempting to authenticate or authorize a user against the LDAP server.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using the
+\fBsetParameter\fP database command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-ldapAuthzQueryTemplate=<string>
+New in version 3.4: Available in MongoDB Enterprise only.
+
+.sp
+A relative LDAP query URL formatted conforming to \fI\%RFC4515\fP and \fI\%RFC4516\fP that \fBmongoldap\fP executes to obtain
+the LDAP groups to which the authenticated user belongs to. The query is
+relative to the host or hosts specified in \fI\%\-\-ldapServers\fP\&.
+.sp
+In the URL, you can use the following substituion tokens:
+.TS
+center;
+|l|l|.
+_
+T{
+Substitution Token
+T}	T{
+Description
+T}
+_
+T{
+\fB{USER}\fP
+T}	T{
+Substitutes the authenticated username, or the
+\fBtransformed\fP
+username if a \fI\%username mapping\fP is specified.
+T}
+_
+T{
+\fB{PROVIDED_USER}\fP
+T}	T{
+Substitutes the supplied username, i.e. before either
+authentication or \fBLDAP transformation\fP\&.
+.sp
+New in version 4.2.
+T}
+_
+.TE
+.sp
+When constructing the query URL, ensure that the order of LDAP parameters
+respects RFC4516:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[ dn  [ ? [attributes] [ ? [scope] [ ? [filter] [ ? [Extensions] ] ] ] ] ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If your query includes an attribute, \fBmongoldap\fP assumes that the query
+retrieves a the DNs which this entity is member of.
+.sp
+If your query does not include an attribute, \fBmongoldap\fP assumes
+the query retrieves all entities which the user is member of.
+.sp
+For each LDAP DN returned by the query, \fBmongoldap\fP assigns the authorized
+user a corresponding role on the \fBadmin\fP database. If a role on the on the
+\fBadmin\fP database exactly matches the DN, \fBmongoldap\fP grants the user the
+roles and privileges assigned to that role. See the
+\fBdb.createRole()\fP method for more information on creating roles.
+.INDENT 7.0
+.INDENT 3.5
+.SH EXAMPLE
+.sp
+This LDAP query returns any groups listed in the LDAP user object\(aqs
+\fBmemberOf\fP attribute.
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+"{USER}?memberOf?base"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Your LDAP configuration may not include the \fBmemberOf\fP attribute as part
+of the user schema, may possess a different attribute for reporting group
+membership, or may not track group membership through attributes.
+Configure your query with respect to your own unique LDAP configuration.
+.UNINDENT
+.UNINDENT
+.sp
+If unset, \fBmongoldap\fP cannot authorize users using LDAP.
+.sp
+This setting can be configured on a running \fBmongoldap\fP using the
+\fBsetParameter\fP database command.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+An explanation of \fI\%RFC4515\fP,
+\fI\%RFC4516\fP or LDAP queries is out
+of scope for the MongoDB Documentation. Please review the RFC directly or
+use your preferred LDAP resource.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SH AUTHOR
+MongoDB Documentation Project
+.SH COPYRIGHT
+2008-2019
+.\" Generated by docutils manpage writer.
+.
diff --git a/debian/mongoreplay.1 b/debian/mongoreplay.1
new file mode 100644
index 00000000000..68448ff9121
--- /dev/null
+++ b/debian/mongoreplay.1
@@ -0,0 +1,1322 @@
+.\" Man page generated from reStructuredText.
+.
+.TH "MONGOREPLAY" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
+.SH NAME
+mongoreplay \- MongoDB Traffic Capture and Replay Tool
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.SS On this page
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Synopsis\fP
+.IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
+\fI\%Required Access\fP
+.IP \(bu 2
+\fI\%Options\fP
+.IP \(bu 2
+\fI\%Commands\fP
+.IP \(bu 2
+\fI\%mongoreplay Report Format\fP
+.IP \(bu 2
+\fI\%Examples\fP
+.UNINDENT
+.SH SYNOPSIS
+.sp
+New in version 3.4.
+
+.INDENT 0.0
+.INDENT 3.5
+.IP "Availability"
+.sp
+Available for Linux and macOS.
+.UNINDENT
+.UNINDENT
+.sp
+\fI\%mongoreplay\fP is a traffic capture and replay tool for MongoDB
+that you can use to inspect and record commands sent to a MongoDB
+instance, and then replay those commands back onto another host at a
+later time.
+.sp
+\fI\%mongoreplay\fP can help you preview how your MongoDB deployment
+will perform a production workload under a different environment,
+such as with a different storage engine, on different hardware, or
+with a different operating system configuration.
+\fI\%mongoreplay\fP can also help reproduce and investigate an issue by
+recording and replaying the operations that trigger the issue.
+Finally, \fI\%mongoreplay\fP serves as a more flexible version of
+the legacy \fBmongosniff\fP tool to help you investigate database activity.
+.sp
+Run \fI\%mongoreplay\fP from the system command line, not the \fBmongo\fP shell.
+.SH AVAILABILITY
+.sp
+The \fI\%mongoreplay\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. The \fBmongoreplay\fP tool is not available on Windows.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
+.SH REQUIRED ACCESS
+.sp
+\fI\%mongoreplay\fP requires access to the network interface that
+the \fI\%record\fP or \fI\%monitor\fP commands will
+listen on. You may need to run \fI\%mongoreplay\fP with root privileges
+to access the network device.
+.sp
+\fI\%mongoreplay\fP will not work with MongoDB instances using an SSL connection.
+.sp
+\fBWARNING:\fP
+.INDENT 0.0
+.INDENT 3.5
+Only use root privileges when connecting to trusted sources.
+.UNINDENT
+.UNINDENT
+.sp
+If you are using \fI\%play\fP to connect to a MongoDB deployment
+that enforces access control, you must
+connect as a user with the required privileges to execute the
+recorded operations. Include the user\(aqs credentials in the
+\fI\%\-\-host\fP MongoDB connection string.
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B mongoreplay
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-verbosity, \-v
+Increases the amount of internal reporting returned on standard output
+or in log files. Increase the verbosity with the \fB\-v\fP form by
+including the option multiple times, (e.g. \fB\-vvvvv\fP\&.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-debug, \-d
+Increases the amount of detail about \fBmongoreplay\fP operations
+and errors recorded
+in log files. Increase the debugging detail with the \fB\-d\fP form by
+including the option multiple times, (e.g. \fB\-ddd\fP\&.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-silent, \-s
+When set, \fBmongoreplay\fP does not produce any log output.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-help
+Returns information on the options and use of \fBmongoreplay\fP\&.
+.UNINDENT
+.SH COMMANDS
+.sp
+\fI\%mongoreplay\fP includes the following \fIcommands\fP to record,
+play back, and monitor MongoDB network traffic.
+.SS \fBmongoreplay record\fP
+.sp
+\fI\%record\fP produces a playback file based on
+network traffic. \fI\%record\fP supports collecting network
+traffic directly or can
+accept a \fI\%pcap file\fP
+to produce the playback file.
+The playback file contains a list of all requests sent to the
+\fBmongod\fP instance during the recording as well as all
+responses transmitted to the client during the recording. The playback
+file also records metadata for each request, such as the connection
+identifier and timestamp.
+.sp
+The following prototype uses \fI\%mongoreplay\fP to record data
+on the loopback network interface and creates a playback file
+located at \fB~/recordings/playback\fP\&.
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay record \-i eth0 \-e "port 27017" \-p ~/recordings/playback
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Similarly, the following prototype uses \fI\%mongoreplay\fP
+to produce a playback file from an existing pcap file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay record \-f traffic.pcap \-p ~/recordings/playback
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBrecord\fP supports the following options:
+.INDENT 0.0
+.TP
+.B mongoreplay record
+.UNINDENT
+.INDENT 0.0
+.TP
+.B record
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-f <path>
+Specifies the path to a pcap file that \fI\%record\fP should read to
+produce a playback file.
+.sp
+Use \fB\-f\fP as an alternative to capturing network traffic using
+\fB\-i\fP\&. You must specify \fIeither\fP \fB\-f\fP or \fB\-i\fP\&. If you include
+both options, \fBmongoreplay record\fP produces an error.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-b <number>
+Size of heap used to merge separate streams together.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-expr <filter expression>, \-e <filter expression>
+An expression in \fI\%Berkeley Packet Filter (BPF) syntax\fP to apply to incoming traffic to
+record. Required if you are capturing traffic from a network interface using
+\fI\%\-i\fP\&.
+.sp
+For example, to capture traffic from a MongoDB instance running on
+port 27017, you would specify \fB\-e \(aqport 27017\(aq\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-i <interface>
+Specifies the network interface that \fI\%record\fP should listen on to
+capture network traffic.
+.sp
+Use with \fI\%\-e\fP\&.
+.sp
+Use \fB\-i\fP as an alternative to reading an existing pcap file with
+\fB\-i\fP\&. You must specify \fIeither\fP \fB\-f\fP or \fB\-i\fP\&. If you include
+both options, \fBmongoreplay record\fP produces an error.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-gzip <boolean>
+If specified, \fI\%record\fP compresses the playback file with gzip.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-playback\-file <path>, \-p <path>
+Specifies the path to which to write the playback file.
+.sp
+The produced playback file is a BSON file.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+.SS See
+.sp
+\fI\%Use record\fP for examples of using
+\fI\%mongoreplay\fP with the \fBrecord\fP command.
+.UNINDENT
+.UNINDENT
+.SS \fBmongoreplay play\fP
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Starting in MongoDB 4.0, \fI\%mongoreplay play\fP supports a new
+\fBMONGOREPLAY_HOST\fP environment variable that specifies the
+MongoDB connection string. The new environment
+vairable can be used instead of the command\-line \fI\%\-\-host\fP option.
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B play
+\fI\%play\fP replays a playback file created with
+\fI\%record\fP against a \fBmongod\fP instance.
+.UNINDENT
+.sp
+For example, the following uses \fI\%mongoreplay play\fP to replay the
+\fB~/recordings/playback\fP playback file to the \fBmongod\fP instance running on
+\fB192.168.0.4:27018\fP:
+.INDENT 0.0
+.IP \(bu 2
+Using the \fI\%\-\-host\fP option:
+.INDENT 2.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay play \-p ~/recordings/playback \-\-report ~/reports/replay_stats.json \-\-host mongodb://192.168.0.4:27018
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP \(bu 2
+Using the \fBMONGOREPLAY_HOST\fP environment variable (Available starting in MongoDB 4.0):
+.INDENT 2.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+export MONGOREPLAY_HOST="mongodb://192.168.0.4:27018"
+mongoreplay play \-p ~/recordings/playback \-\-report ~/reports/replay_stats.json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS \fBplay\fP Options
+.sp
+\fBplay\fP supports the following options:
+.INDENT 0.0
+.TP
+.B mongoreplay play
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-collect <json|format|none>
+\fIDefault\fP: format
+.sp
+Specifies the output format for the collected statistics.
+.INDENT 7.0
+.IP \(bu 2
+\fBjson\fP: outputs stat information as json
+.IP \(bu 2
+\fBformat\fP: uses the formatting specified in the \fB\-\-format\fP option
+to produce the output file.
+.IP \(bu 2
+\fBnone\fP: does not provide any output
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-report <path>
+Specifies the path to which to write an execution report.
+Use \fI\%\-\-collect\fP to specify the output format for the report.
+.sp
+If you do not specify \fB\-\-report\fP, \fI\%play\fP writes to STDOUT.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-no\-truncate
+If specified, disables truncation of large reply payload data in the
+\fI\%play\fP log output.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-format
+\fIDefault\fP: \fB%F{blue}%t%f %F{cyan}(Connection: %o:%i)%f %F{yellow}%l%f
+%F{red}%T %c%f %F{white}%n%f
+%F{green}%Q{Request:}%f%q%F{green}%R{Response:}%f%r)\fP
+.sp
+Specifies the format for terminal output.
+You can specify arguments immediately after the format \(aqverbs\(aq by wrapping
+them in curly braces, as in \fB%Q{<arg>}\fP\&.
+.sp
+If you specify \fI\%\-\-format\fP, also specify \fBformat\fP as the value for the
+\fI\%\-\-collect\fP option.
+.sp
+\fI\%\-\-format\fP supports the following verbs:
+.INDENT 7.0
+.IP \(bu 2
+\fB%n\fP: namespace
+.IP \(bu 2
+\fB%l\fP: latency
+.IP \(bu 2
+\fB%t\fP: time. You may optionally specify the date layout using the
+Go Programming Language\(aqs \fI\%time formatting\fP\&. Go
+uses \fBMon Jan 2 15:04:05 MST 2006\fP as its reference time. You
+must specify the time format using the reference time. Thus, if you
+wanted to print the date in format \fByyyy\-mm\-dd hh:mm\fP, you would
+specify \fB%t{2006\-01\-02 15:04}\fP\&. Refer to the Go \fI\%time formatting\fP
+documentation for more information.
+.IP \(bu 2
+\fB%T\fP: op time
+.IP \(bu 2
+\fB%c\fP: command
+.IP \(bu 2
+\fB%o\fP: number of connections
+.IP \(bu 2
+\fB%i\fP: request ID
+.IP \(bu 2
+\fB%q\fP: request. You may optinally specified a dot\-delimited field
+within the JSON structure, as in, \fB%q{command_args.documents}\fP\&.
+.IP \(bu 2
+\fB%r\fP: response. You may optinally specified a dot\-delimited field
+within the JSON structure, as in, \fB%q{command_args.documents}\fP\&.
+.IP \(bu 2
+\fB%Q{<arg>}\fP: display \fB<arg>\fP on presence of request data
+.IP \(bu 2
+\fB%R{<arg>}\fP: display \fB<arg>\fP on presence of response data
+.UNINDENT
+.sp
+In addition, \fI\%\-\-format\fP supports the following start/end ANSI escape sequences:
+.INDENT 7.0
+.IP \(bu 2
+\fB%B\fP/\fB%b\fP: bold
+.IP \(bu 2
+\fB%U\fP/\fB%u\fP: underline
+.IP \(bu 2
+\fB%S\fP/\fB%s\fP: standout
+.IP \(bu 2
+\fB%F\fP/\fB%f\fP: text color (required arg \-\- word or number, 8\-color)
+.IP \(bu 2
+\fB%K\fP/\fB%k\fP: background color (required arg \-\- same as %F/%f)
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-no\-colors
+When set, removes colors from the \fI\%default format\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-playback\-file <path>, \-p <path>
+Specifies the path from which to read the playback file.
+.sp
+If the playback file was created using the \fI\%\-\-gzip\fP option, you must also specify \fB\-\-gzip\fP
+when running \fI\%play\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-speed number
+\fIDefault\fP: 1.0
+.sp
+Specifies a multiplier to adjust playback speed. \fB\-\-speed 1.0\fP
+processes the playback file in real time; \fB\-\-speed 0.5\fP at half
+speed; \fB\-\-speed 3.0\fP at triple speed.
+.sp
+The specified speed is a \fItarget\fP speed. If \fBmongoreplay play\fP encounters
+a bottleneck, playback may be slower than the specified multiplier.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-host <uri connection string>
+\fIDefault\fP: mongodb://localhost:27017
+.sp
+Specifies a MongoDB connection string
+for the MongoDB deployment to which to
+play back the captured network traffic.
+.sp
+By default, \fI\%play\fP
+attempts to connect to a \fBmongod\fP instance running on the localhost on
+port number \fB27017\fP\&.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Starting in MongoDB 4.0, \fI\%mongoreplay play\fP supports a new
+\fBMONGOREPLAY_HOST\fP environment variable that specifies the
+connection string for the MongoDB deployment. The new environment
+vairable can be used instead of the command\-line \fI\%\-\-host\fP option.
+.sp
+If \fI\%\-\-host\fP command\-line option is
+specified, the \fI\%\-\-host\fP value overrides
+the environment variable.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-repeat number
+\fIDefault\fP: 1
+.sp
+Specifies the number of times to play the playback file.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-queueTime number
+\fIDefault\fP: 15
+.sp
+Specifies the maximum time, in seconds, to queue operations in advance
+of transmitting them.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-no\-preprocess
+When set, \fI\%play\fP does not preprocess the input file to pre\-map
+data such as MongoDB cursor IDs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-gzip <boolean>
+If specified, \fI\%play\fP decompresses the playback file with gzip.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+.SS See
+.sp
+\fI\%Use play\fP for examples of using
+\fI\%mongoreplay\fP with the \fI\%play\fP command.
+.UNINDENT
+.UNINDENT
+.SS \fBmongoreplay monitor\fP
+.sp
+\fI\%monitor\fP inspects live or pre\-recorded
+MongoDB network traffic.
+.sp
+The following prototype uses \fI\%mongoreplay\fP to produce a
+JSON report based on the \fBplayback.bson\fP playback file in the \fB~/recordings\fP directory:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay monitor \-\-collect json \-\-report ~/reports/monitor\-report.json \-p ~/recordings/playback.bson
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBmonitor\fP supports the following options:
+.INDENT 0.0
+.TP
+.B mongoreplay monitor
+.UNINDENT
+.INDENT 0.0
+.TP
+.B monitor
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-collect <json|format|none>
+\fIDefault\fP: format
+.sp
+Specifies the output format for the collected statistics.
+.INDENT 7.0
+.IP \(bu 2
+\fBjson\fP: outputs stat information as json
+.IP \(bu 2
+\fBformat\fP: uses the formatting specified in the \fB\-\-format\fP option
+to produce the output file.
+.IP \(bu 2
+\fBnone\fP: does not provide any output
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-report <path>
+Specifies the path to which to write an execution report.
+Use \fI\%\-\-collect\fP to specify the output format for the report.
+.sp
+If you do not specify \fB\-\-report\fP, \fI\%monitor\fP writes to STDOUT.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-no\-truncate
+If specified, disables truncation of large reply payload data in the
+\fI\%monitor\fP log output.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-format
+\fIDefault\fP: \fB%F{blue}%t%f %F{cyan}(Connection: %o:%i)%f %F{yellow}%l%f
+%F{red}%T %c%f %F{white}%n%f
+%F{green}%Q{Request:}%f%q%F{green}%R{Response:}%f%r)\fP
+.sp
+Specifies the format for terminal output.
+You can specify arguments immediately after the format \(aqverbs\(aq by wrapping
+them in curly braces, as in \fB%Q{<arg>}\fP\&.
+.sp
+If you specify \fI\%\-\-format\fP, also specify \fBformat\fP as the value for the
+\fI\%\-\-collect\fP option.
+.sp
+\fI\%\-\-format\fP supports the following verbs:
+.INDENT 7.0
+.IP \(bu 2
+\fB%n\fP: namespace
+.IP \(bu 2
+\fB%l\fP: latency
+.IP \(bu 2
+\fB%t\fP: time. You may optionally specify the date layout using the
+Go Programming Language\(aqs \fI\%time formatting\fP\&. Go
+uses \fBMon Jan 2 15:04:05 MST 2006\fP as its reference time. You
+must specify the time format using the reference time. Thus, if you
+wanted to print the date in format \fByyyy\-mm\-dd hh:mm\fP, you would
+specify \fB%t{2006\-01\-02 15:04}\fP\&. Refer to the Go \fI\%time formatting\fP
+documentation for more information.
+.IP \(bu 2
+\fB%T\fP: op time
+.IP \(bu 2
+\fB%c\fP: command
+.IP \(bu 2
+\fB%o\fP: number of connections
+.IP \(bu 2
+\fB%i\fP: request ID
+.IP \(bu 2
+\fB%q\fP: request. You may optinally specified a dot\-delimited field
+within the JSON structure, as in, \fB%q{command_args.documents}\fP\&.
+.IP \(bu 2
+\fB%r\fP: response. You may optinally specified a dot\-delimited field
+within the JSON structure, as in, \fB%q{command_args.documents}\fP\&.
+.IP \(bu 2
+\fB%Q{<arg>}\fP: display \fB<arg>\fP on presence of request data
+.IP \(bu 2
+\fB%R{<arg>}\fP: display \fB<arg>\fP on presence of response data
+.UNINDENT
+.sp
+In addition, \fI\%\-\-format\fP supports the following start/end ANSI escape sequences:
+.INDENT 7.0
+.IP \(bu 2
+\fB%B\fP/\fB%b\fP: bold
+.IP \(bu 2
+\fB%U\fP/\fB%u\fP: underline
+.IP \(bu 2
+\fB%S\fP/\fB%s\fP: standout
+.IP \(bu 2
+\fB%F\fP/\fB%f\fP: text color (required arg \-\- word or number, 8\-color)
+.IP \(bu 2
+\fB%K\fP/\fB%k\fP: background color (required arg \-\- same as %F/%f)
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-no\-colors
+When set, removes colors from the \fI\%default format\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-f <path>
+Specifies the path to a pcap file that \fI\%monitor\fP should read to
+produce a playback file.
+.sp
+Use \fB\-f\fP as an alternative to capturing network traffic using
+\fB\-i\fP\&. You must specify \fIeither\fP \fB\-f\fP or \fB\-i\fP\&. If you include
+both options, \fBmongoreplay monitor\fP produces an error.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-b <number>
+Size of heap used to merge separate streams together.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-expr <filter expression>, \-e <filter expression>
+An expression in \fI\%Berkeley Packet Filter (BPF) syntax\fP to apply to incoming traffic to
+record. Required if you are capturing traffic from a network interface using
+\fI\%\-i\fP\&.
+.sp
+For example, to capture traffic from a MongoDB instance running on
+port 27017, you would specify \fB\-e \(aqport 27017\(aq\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-i <interface>
+Specifies the network interface that \fI\%monitor\fP should listen on to
+capture network traffic.
+.sp
+Use with \fI\%\-e\fP\&.
+.sp
+Use \fB\-i\fP as an alternative to reading an existing pcap file with
+\fB\-i\fP\&. You must specify \fIeither\fP \fB\-f\fP or \fB\-i\fP\&. If you include
+both options, \fBmongoreplay monitor\fP produces an error.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-paired
+When specified, \fI\%monitor\fP outputs one line for each request/reply pair record.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-gzip <boolean>
+If specified, \fI\%monitor\fP decompresses the playback file with gzip.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-playback\-file <path>, \-p <path>
+Specifies the path from which to read the playback file.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+.SS See
+.sp
+\fI\%Use monitor\fP for examples of using
+\fI\%mongoreplay\fP with the \fI\%monitor\fP command.
+.UNINDENT
+.UNINDENT
+.SH MONGOREPLAY REPORT FORMAT
+.sp
+\fI\%monitor\fP and \fI\%play\fP can produce
+reports based on a playback file when run with the \fB\-\-report\fP option.
+.SS Sample Record
+.sp
+The following is an example record from a JSON\-formatted
+\fI\%monitor\fP report:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+   "order" : 21,
+   "op" : "op_msg",
+   "command" : "aggregate",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "aggregate" : "foo",
+               "cursor" : {},
+               "lsid" : {
+                  "id" : {
+                     "$binary" : "eBZNIaAbRTiAoWkaNZ0T8Q==",
+                     "$type" : "04"
+                  }
+               },
+               "pipeline" : [
+                  { "$match" : { "borough" : "Queens" } },
+                  { "$group" : { "_id" : "$cuisine", "count" : { "$sum": 1 } } }
+               ]
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "connection_num" : 0,
+   "seen" : "2018\-11\-15T14:07:07.136794\-05:00",
+   "request_id" : 25
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Fields
+.sp
+\fI\%mongoreplay\fP reports can include the following fields:
+.INDENT 0.0
+.TP
+.B order
+A monotonically increasing key indicating the order in which the
+operations were recorded and played back. This can be used to
+reconstruct the ordering of the series of operations executed on a
+connection, since the order in which they appear in the report file
+may not match the playback order.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B op
+The type of operation represented by the request: i.e. "query",
+"insert", "command", "getmore".
+.UNINDENT
+.INDENT 0.0
+.TP
+.B command
+The name of the database command performed, such as \fBisMaster\fP or
+\fBgetLastError\fP\&. This field is left blank for operations that are not
+commands, such as queries and inserts.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B ns
+The namespace on which the request was executed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B request_data
+The payload of the operation.
+.INDENT 7.0
+.IP \(bu 2
+Query operations: \fBrequest_data\fP contains the actual
+query that was issued.
+.IP \(bu 2
+Insert operations: \fBrequest_data\fP contains the documents
+being inserted.
+.IP \(bu 2
+Update operations: \fBrequest_data\fP contains the query
+selector and the update modifier.
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B reply_data
+The payload of the reply to the request.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B nreturned
+The number of documents returned as a result of the operation.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B played_at
+The time at which the \fI\%play\fP command executed
+the operation.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B play_at
+The time at which the operation was supposed to be executed by
+the \fI\%play\fP command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B playbacklag_us
+The difference in microseconds in time between \fBplayed_at\fP
+and \fBplay_at\fP\&. Higher values generally indicate that the
+target server is not able to keep up with the rate at which requests
+need to be executed according to the playback file.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B connection_num
+A key that identifies the connection on which the request was
+executed. All requests/replies that executed on the same connection
+have the same value for \fBconnection_num\fP\&.
+.sp
+The \fBconnection_num\fP value
+does \fInot\fP match the connection ID logged on the server side.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B latency_us
+The time difference in microseconds between when the request was
+sent by the client and when a response from the server was received.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B errors
+Lists any errors returned from the server.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B msg
+Lists the error message returned from the server.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B seen
+The time at which the operation was originally captured.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B request_id
+The ID of the MongoDB operation. The \fBrequest_id\fP for a request
+operation is the same as the \fBresponse_id\fP for the corresponding
+reply.
+.UNINDENT
+.SS Output Formatting with \fB\-\-format\fP
+.sp
+\fI\%monitor\fP and \fI\%play\fP output to either the
+terminal or, when run with \fB\-\-report\fP (i.e. \fI\%monitor \-\-report\fP or \fI\%play \-\-report\fP), to a file.
+.sp
+Use the \fB\-\-collect\fP (\fI\%monitor \-\-collect\fP or \fI\%play \-\-collect\fP)
+option to specify the format of the output:
+.INDENT 0.0
+.IP \(bu 2
+\fB\-\-collect json\fP produces JSON output,
+.IP \(bu 2
+\fB\-\-collect format\fP outputs the data based on the formatting
+specified by the \fB\-\-format\fP option for \fI\%monitor\fP and \fI\%play\fP .
+.UNINDENT
+.SH EXAMPLES
+.SS Use \fI\%record\fP
+.SS Capture TCP data with \fBrecord\fP
+.sp
+To create a recording of traffic, use the \fI\%record\fP command. The
+following operation records traffic through port \fB27017\fP on the
+\fBeth0\fP network interface and writes the captured traffic to
+\fB~/recordings/recording.bson\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay record \-i eth0 \-e "port 27017" \-p ~/recordings/recording.bson
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The produced playback file contains everything needed to re\-execute
+the workload on another system.
+.SS Record a Playback File from Existing pcap Data
+.sp
+If you do not wish to use \fI\%mongoreplay\fP to capture traffic, you
+can capture traffic using a utility such as \fBtcpdump\fP and then create a
+\fI\%mongoreplay\fP recording from the static pcap file.
+.sp
+\fBWARNING:\fP
+.INDENT 0.0
+.INDENT 3.5
+Only use root privileges when connecting to a trusted source.
+.UNINDENT
+.UNINDENT
+.sp
+The following operation uses \fBtcpdump\fP to capture traffic through
+port \fB27017\fP on the \fBeth0\fP network interface and writes the captured
+data to a pcap file called \fBtraffic.pcap\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+sudo tcpdump \-B $((100*1024)) \-i eth0 \-n "port 27017" \-w traffic.pcap
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+To create the \fI\%mongoreplay\fP playback file, you can use
+\fI\%record\fP with the \fI\%\-f\fP
+option to specify the pcap file from which to create the playback file,
+as in the following:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay record \-f traffic.pcap \-p ~/recordings/playback.bson
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The produced playback file contains everything needed to re\-execute
+the workload on another system.
+.SS Use \fI\%play\fP
+.SS Execute a Playback File Against a Target Host
+.sp
+\fI\%play\fP takes a playback file and executes the
+recorded operations against the \fBmongodb://example.com:27018\fP host.
+Since the \fBmongod\fP enforces authentication, the
+connection string specified to
+\fI\%\-\-host\fP also includes the username, password, and authentication
+database so that \fI\%mongoreplay\fP can write to the database.
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay play \-p ~/recordings/recording.bson \-\-host mongodb://username:password@example.com:27018/admin
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+By default, \fB~bin.play\fP executes the playback
+file at the rate of the recording. \fI\%\-\-speed\fP lets you modify
+the playback speed. For example, the following operation executes
+the operations in \fBrecording.bson\fP at twice the recording speed:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay play \-p ~/recordings/recording.bson \-\-speed=2.0 \-\-host mongodb://username:password@example.com:27018/admin
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Log Metrics About Execution Performance during Playback
+.sp
+\fI\%play\fP can produce a report with detailed metrics
+about the performance of each operation executed during playback.
+.sp
+The following example executes playback against the
+\fBmongodb://example.com:27017\fP host and produces a JSON report written to
+\fB~/reports/playback\-report.json\fP
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay play \-p ~/recordings/recording.bson \-\-report ~/reports/playback\-report.json \-\-collect json \-\-host mongodb://example.com:27017
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The \fBplay\fP report contents would resemble:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+   "order" : 0,
+   "op" : "op_msg",
+   "command" : "isMaster",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "forShell" : 1,
+               "isMaster" : 1
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "reply_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "ismaster" : true,
+               "localTime" : {
+                  "$date" : "2018\-11\-15T21:35:01.843Z"
+               },
+               "logicalSessionTimeoutMinutes" : 30,
+               "maxBsonObjectSize" : 16777216,
+               "maxMessageSizeBytes" : 48000000,
+               "maxWireVersion" : 7,
+               "maxWriteBatchSize" : 100000,
+               "minWireVersion" : 0,
+               "ok" : 1,
+               "readOnly" : false
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "played_at" : "2018\-11\-15T16:35:01.84304\-05:00",
+   "play_at" : "2018\-11\-15T16:35:01.842903\-05:00",
+   "playbacklag_us" : 137,
+   "connection_num" : 1,
+   "latency_us" : 151,
+   "seen" : "2018\-11\-15T21:30:33.379675Z",
+   "request_id" : 21
+}
+{
+   "order" : 2,
+   "op" : "op_msg",
+   "command" : "listCollections",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "authorizedCollections" : true,
+               "filter" : {
+
+               },
+               "listCollections" : 1,
+               "lsid" : {
+                  "id" : {
+                     "$binary" : "esmcqhiXSIWSpKGb4sOekw==",
+                     "$type" : "04"
+                  }
+               },
+               "nameOnly" : true
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "reply_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "cursor" : {
+                  "firstBatch" : [ ],
+                  "id" : {
+                     "$numberLong" : "0"
+                  },
+                  "ns" : "test.$cmd.listCollections"
+               },
+               "ok" : 1
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "played_at" : "2018\-11\-15T16:35:08.715002\-05:00",
+   "play_at" : "2018\-11\-15T16:35:08.713539\-05:00",
+   "playbacklag_us" : 1463,
+   "connection_num" : 1,
+   "latency_us" : 331,
+   "seen" : "2018\-11\-15T21:30:40.250311Z",
+   "request_id" : 22
+}
+{
+   "order" : 4,
+   "op" : "op_msg",
+   "command" : "isMaster",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "forShell" : 1,
+               "isMaster" : 1
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "reply_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "ismaster" : true,
+               "localTime" : {
+                  "$date" : "2018\-11\-15T21:35:08.715Z"
+               },
+               "logicalSessionTimeoutMinutes" : 30,
+               "maxBsonObjectSize" : 16777216,
+               "maxMessageSizeBytes" : 48000000,
+               "maxWireVersion" : 7,
+               "maxWriteBatchSize" : 100000,
+               "minWireVersion" : 0,
+               "ok" : 1,
+               "readOnly" : false
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "played_at" : "2018\-11\-15T16:35:08.715554\-05:00",
+   "play_at" : "2018\-11\-15T16:35:08.71471\-05:00",
+   "playbacklag_us" : 844,
+   "connection_num" : 1,
+   "latency_us" : 208,
+   "seen" : "2018\-11\-15T21:30:40.251482Z",
+   "request_id" : 23
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Refer to \fI\%mongoreplay Report Format\fP for a description of each field.
+.SS Use \fI\%monitor\fP
+.SS Inspect Recorded Operations
+.sp
+\fI\%monitor\fP can create a report based on the
+contents of a playback file. \fI\%monitor\fP\(aqs report includes
+\fIall\fP operations and some metadata about each operation\(aqs execution.
+.sp
+The following operation uses \fI\%monitor\fP to create a JSON
+report based on the contents of the \fBrecording.bson\fP playback file
+located in the \fB~/recordings\fP directory and write the report to
+\fB~/reports/monitoring\-report.json\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay monitor \-p ~/recordings/recording.bson \-\-report ~/reports/monitoring\-report.json \-\-collect json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The report contents would resemble:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+   "order" : 0,
+   "op" : "op_msg",
+   "command" : "isMaster",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "forShell" : 1,
+               "isMaster" : 1
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "connection_num" : 0,
+   "seen" : "2018\-11\-15T21:30:33.379675Z",
+   "request_id" : 21
+}
+{
+   "order" : 1,
+   "op" : "op_msg",
+   "command" : "aggregate",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "aggregate" : "restaurants",
+               "cursor" : {
+
+               },
+               "lsid" : {
+                  "id" : {
+                     "$binary" : "esmcqhiXSIWSpKGb4sOekw==",
+                     "$type" : "04"
+                  }
+               },
+               "pipeline" : [
+                  {
+                     "$match" : {
+                        "borough" : "Manhattan"
+                     }
+                  },
+                  {
+                     "$group" : {
+                        "_id" : "$cuisine"
+                     }
+                  }
+               ]
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "connection_num" : 0,
+   "seen" : "2018\-11\-15T16:28:52.870007\-05:00",
+   "request_id" : 13
+}
+{
+   "order" : 1,
+   "op" : "op_msg",
+   "command" : "reply",
+   "reply_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "ismaster" : true,
+               "localTime" : {
+                  "$date" : "2018\-11\-15T21:30:33.379Z"
+               },
+               "logicalSessionTimeoutMinutes" : 30,
+               "maxBsonObjectSize" : 16777216,
+               "maxMessageSizeBytes" : 48000000,
+               "maxWireVersion" : 7,
+               "maxWriteBatchSize" : 100000,
+               "minWireVersion" : 0,
+               "ok" : 1,
+               "readOnly" : false
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "connection_num" : 0,
+   "latency_us" : 174,
+   "seen" : "2018\-11\-15T21:30:33.379849Z",
+   "request_id" : 21
+}
+{
+   "order" : 2,
+   "op" : "op_msg",
+   "command" : "listCollections",
+   "ns" : "test",
+   "request_data" : {
+      "sections" : [
+         {
+            "payload" : {
+               "$db" : "test",
+               "authorizedCollections" : true,
+               "filter" : {
+
+               },
+               "listCollections" : 1,
+               "lsid" : {
+                  "id" : {
+                     "$binary" : "esmcqhiXSIWSpKGb4sOekw==",
+                     "$type" : "04"
+                  }
+               },
+               "nameOnly" : true
+            },
+            "payloadType" : 0
+         }
+      ]
+   },
+   "connection_num" : 0,
+   "seen" : "2018\-11\-15T21:30:40.250311Z",
+   "request_id" : 22
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Refer to \fI\%mongoreplay Report Format\fP for a description of each field.
+.SS Inspect Live MongoDB Traffic
+.sp
+\fI\%monitor\fP can also inspect live traffic and, optionally,
+create a report based on the observed operations.
+.sp
+To monitor traffic in real time in your terminal, omit the
+\fI\%\-\-report\fP option, as in the
+following:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay monitor \-i eth0 \-e \(aqport 27017\(aq \-\-collect json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Optionally, you can create a report based on the operations observed
+using \fI\%monitor\fP\&. The following example creates a JSON
+report written to \fB~/reports/monitor\-live.json\fP based on the traffic
+through port \fB27017\fP on the \fBeth0\fP network interface:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+mongoreplay monitor \-i eth0 \-e \(aqport 27017\(aq \-\-report ~/reports/monitor\-live.json \-\-collect json
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SH AUTHOR
+MongoDB Documentation Project
+.SH COPYRIGHT
+2008-2019
+.\" Generated by docutils manpage writer.
+.
diff --git a/debian/mongorestore.1 b/debian/mongorestore.1
index ce2e6bd4b2c..dce29ebb4ae 100644
--- a/debian/mongorestore.1
+++ b/debian/mongorestore.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGORESTORE" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGORESTORE" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongorestore \- MongoDB Data Restoration Tool
 .
@@ -35,6 +35,10 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
+\fI\%Usage in Backup Strategy\fP
+.IP \(bu 2
 \fI\%Syntax\fP
 .IP \(bu 2
 \fI\%Behavior\fP
@@ -59,9 +63,52 @@ The \fI\%mongorestore\fP program loads data from either a binary
 database dump created by \fBmongodump\fP or the standard input
 (starting in version 3.0.0) into a \fBmongod\fP or
 \fBmongos\fP instance.
+.SH AVAILABILITY
+.sp
+The \fI\%mongorestore\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
 .sp
-For an overview of \fI\%mongorestore\fP usage, see
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
+.SH USAGE IN BACKUP STRATEGY
+.SS Standalones/Replica Sets
+.sp
+For an overview of \fI\%mongorestore\fP usage as part of a
+backup and recovery strategy, see
 /tutorial/backup\-and\-restore\-tools\&.
+.SS Sharded Clusters
+.sp
+\fBmongodump\fP and \fI\%mongorestore\fP
+\fBcannot\fP be part of a backup strategy for 4.2+ sharded clusters
+that have sharded transactions in progress as these tools cannot
+guarantee a atomicity guarantees of data across the shards.
+.sp
+For 4.2+ sharded clusters with in\-progress sharded transactions, for
+coordinated backup and restore processes that maintain the atomicity
+guarantees of transactions across shards, see:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%MongoDB Atlas\fP,
+.IP \(bu 2
+\fI\%MongoDB Cloud Manager\fP, or
+.IP \(bu 2
+\fI\%MongoDB Ops Manager\fP\&.
+.UNINDENT
 .SH SYNTAX
 .sp
 Run \fI\%mongorestore\fP from the system command line, not the \fBmongo\fP shell.
@@ -122,7 +169,7 @@ directory:
 .sp
 .nf
 .ft C
-mongorestore \-\-nsInclude test.purchaseorders dump/
+mongorestore \-\-nsInclude=test.purchaseorders dump/
 .ft P
 .fi
 .UNINDENT
@@ -137,7 +184,7 @@ corresponding data in the \fBdump/\fP directory:
 .sp
 .nf
 .ft C
-mongorestore \-\-nsInclude foo.bar dump/
+mongorestore \-\-nsInclude=foo.bar dump/
 .ft P
 .fi
 .UNINDENT
@@ -210,7 +257,7 @@ configured to use FIPS mode\&.
 .sp
 Starting in version 4.2, if you specify write concern in both the
 \fI\%\-\-writeConcern\fP option and the
-\fI\%\-\-uri connection string\fP option, the
+\fI\%\-\-uri\fP connection string option, the
 \fI\%\-\-writeConcern\fP value overrides
 the write concern specified in the URI string.
 .sp
@@ -218,9 +265,21 @@ In earlier versions, the two options are incompatible.
 .SH REQUIRED ACCESS
 .sp
 To restore data to a MongoDB deployment that has access control enabled, the \fBrestore\fP role provides
-access to restore any database if the backup data does not include
-\fBsystem.profile\fP collection data.
+the necessary privileges to restore data from backups \fIif\fP the data does
+not include \fBsystem.profile\fP
+collection data and you run \fI\%mongorestore\fP without the
+\fI\%\-\-oplogReplay\fP option.
 .sp
+If the backup data includes \fBsystem.profile\fP collection data or you run with
+\fI\%\-\-oplogReplay\fP, you need
+additional privileges:
+.TS
+center;
+|l|l|.
+_
+T{
+\fBsystem.profile\fP
+T}	T{
 If the backup data includes \fBsystem.profile\fP collection data and the target database
 does not contain the \fBsystem.profile\fP
 collection, \fI\%mongorestore\fP attempts to create the collection
@@ -230,14 +289,21 @@ documents. As such, the user requires additional privileges to perform
 actions on the \fBsystem.profile\fP
 collection for a database.
 .sp
-As of MongoDB 3.2.11, you can run \fI\%mongorestore\fP with
-\fI\%\-\-oplogReplay\fP if you have the
-\fBrestore\fP role. To replay the oplog on versions of MongoDB
-3.2.10 and earlier, you must create a
-user\-defined role that has
-\fBanyAction\fP on resource\-anyresource and grant only
-to users who must run \fI\%mongorestore\fP with
-\fI\%\-\-oplogReplay\fP\&.
+Both the built\-in roles \fBdbAdmin\fP and
+\fBdbAdminAnyDatabase\fP provide the additional privileges.
+T}
+_
+T{
+\fB\-\-oplogReplay\fP
+T}	T{
+To run with \fI\%\-\-oplogReplay\fP, create a user\-defined role that has \fBanyAction\fP on
+resource\-anyresource\&.
+.sp
+Grant only to users who must run \fI\%mongorestore\fP
+with \fI\%\-\-oplogReplay\fP\&.
+T}
+_
+.TE
 .SH OPTIONS
 .sp
 Changed in version 3.0.0: \fI\%mongorestore\fP removed the \fB\-\-filter\fP, \fB\-\-dbpath\fP, and the
@@ -284,7 +350,7 @@ Returns the \fBmongorestore\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -295,7 +361,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -343,7 +409,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>, \-h <hostname><:port>
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
 \fIDefault\fP: localhost:27017
 .sp
 Specifies a resolvable hostname for the \fBmongod\fP to which to
@@ -358,7 +424,7 @@ the following:
 .sp
 .nf
 .ft C
-\-\-host <replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
+\-\-host=<replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
@@ -374,7 +440,7 @@ the host and port of only that member:
 .sp
 .nf
 .ft C
-\-\-host <hostname1><:port>
+\-\-host=<hostname1><:port>
 .ft P
 .fi
 .UNINDENT
@@ -394,7 +460,7 @@ You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -422,7 +488,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -463,7 +529,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -482,7 +548,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
@@ -501,7 +567,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -533,8 +599,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -577,7 +641,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
+.B \-\-username=<username>, \-u=<username>
 Specifies a username with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -591,7 +655,7 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
+.B \-\-password=<password>, \-p=<password>
 Specifies a password with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -599,7 +663,7 @@ that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 Changed in version 3.0.2: To prompt the user
 for the password, pass the \fI\%\-\-username\fP option without
 \fI\%\-\-password\fP or specify an empty string as the \fI\%\-\-password\fP value,
-as in \fB\-\-password ""\fP .
+as in \fB\-\-password=""\fP .
 
 .sp
 \fBNOTE:\fP
@@ -611,7 +675,7 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
+.B \-\-authenticationDatabase=<dbname>
 Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
 See user\-authentication\-database\&.
 .sp
@@ -624,7 +688,7 @@ You cannot specify both \fI\%\-\-authenticationDatabase\fP and \fI\%\-\-uri\fP\&
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongorestore\fP instance uses to
@@ -699,7 +763,7 @@ You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiServiceName
+.B \-\-gssapiServiceName=<serviceName>
 New in version 2.6.
 
 .sp
@@ -710,7 +774,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiHostName
+.B \-\-gssapiHostName=<hostname>
 New in version 2.6.
 
 .sp
@@ -721,7 +785,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-db <database>, \-d <database>
+.B \-\-db=<database>, \-d=<database>
 Specifies the destination database for \fBmongorestore\fP to restore data
 \fIinto\fP when restoring from a BSON file. If the database does not
 exist, \fBmongorestore\fP creates the database. For example, the following
@@ -731,7 +795,7 @@ restores the \fBsalaries\fP collection into the \fBreporting\fP database.
 .sp
 .nf
 .ft C
-mongorestore \-\-db reporting dump/test/salaries.bson
+mongorestore \-\-db=reporting dump/test/salaries.bson
 .ft P
 .fi
 .UNINDENT
@@ -754,7 +818,7 @@ You cannot specify both \fI\%\-\-db\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-collection <collection>, \-c <collection>
+.B \-\-collection=<collection>, \-c=<collection>
 Specifies the name of the destination collection for \fBmongorestore\fP to
 restore data \fIinto\fP when restoring from a BSON file. If
 you do not specify \fI\%\-\-collection\fP, \fBmongorestore\fP takes
@@ -766,7 +830,7 @@ name.
 .sp
 .nf
 .ft C
-mongorestore \-\-db reporting \-\-collection employeesalaries dump/test/salaries.bson
+mongorestore \-\-db=reporting \-\-collection=employeesalaries dump/test/salaries.bson
 .ft P
 .fi
 .UNINDENT
@@ -779,7 +843,7 @@ Instead, to restore from an archive or a directory, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-nsExclude <namespace pattern>
+.B \-\-nsExclude=<namespace pattern>
 New in version 3.4.
 
 .sp
@@ -794,7 +858,7 @@ patterns.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-nsInclude <namespace pattern>
+.B \-\-nsInclude=<namespace pattern>
 New in version 3.4.
 
 .sp
@@ -810,10 +874,19 @@ patterns.
 If source directory or file (i.e. the directory/file from which you
 are restoring the data) does not contain data files that match the
 namespace pattern, no data will be restored.
+.sp
+For collection names that contain non\-ascii characters,
+\fBmongodump\fP outputs the corresponding filenames with
+percent\-encoded names. However, to restore these collections, do not
+use the encoded names. Instead, use the namespace with the non\-ascii
+characters.
+.sp
+For example, if the dump directory contains
+\fBdump/test/caf%C3%A9s.bson\fP, specify \fB\-\-nsInclude "test.cafés"\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-nsFrom <namespace pattern>
+.B \-\-nsFrom=<namespace pattern>
 New in version 3.4.
 
 .sp
@@ -843,7 +916,7 @@ sign\-delimited wild cards do \fBnot\fP need to be linear.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-nsTo <namespace pattern>
+.B \-\-nsTo=<namespace pattern>
 New in version 3.4.
 
 .sp
@@ -911,7 +984,7 @@ more detailed summary information.
 After restoring the database dump, replays the oplog entries
 from a bson file.
 When used in conjunction with \fBmongodump \-\-oplog\fP,
-\fB~bin.mongorestore \-\-oplogReplay\fP
+\fBmongorestore \-\-oplogReplay\fP
 restores the database to the point\-in\-time backup captured with the
 \fBmongodump \-\-oplog\fP command.
 .sp
@@ -983,7 +1056,7 @@ the following options to limit the data be restored:
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-oplogLimit <timestamp>
+.B \-\-oplogLimit=<timestamp>
 Prevents \fBmongorestore\fP from applying oplog entries
 with timestamp newer than or equal to \fB<timestamp>\fP\&. Specify
 \fB<timestamp>\fP values in the form of \fB<time_t>:<ordinal>\fP, where
@@ -996,7 +1069,7 @@ You must use \fI\%\-\-oplogLimit\fP in conjunction with the
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-oplogFile <path>
+.B \-\-oplogFile=<path>
 New in version 3.4.
 
 .sp
@@ -1035,7 +1108,7 @@ Restore user and role definitions for the given database. See
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-writeConcern <document>
+.B \-\-writeConcern=<document>
 \fIDefault\fP: majority
 .sp
 Specifies the write concern for each write operation that \fBmongorestore\fP
@@ -1047,7 +1120,7 @@ Specify the write concern as a document with w options:
 .sp
 .nf
 .ft C
-\-\-writeConcern "{w:\(aqmajority\(aq}"
+\-\-writeConcern="{w:\(aqmajority\(aq}"
 .ft P
 .fi
 .UNINDENT
@@ -1063,13 +1136,28 @@ the URI string.
 .B \-\-maintainInsertionOrder
 \fIDefault\fP: False
 .sp
-If specified, \fBmongorestore\fP inserts the documents in the order of
-their appearance in the input source, otherwise \fBmongorestore\fP may
-perform the insertions in an arbitrary order.
+If specified,
+.INDENT 7.0
+.IP \(bu 2
+Starting in version 4.2, \fBmongorestore\fP inserts the documents in the
+order of their appearance in the input source. That is, both the
+bulk write batch order and document order within the batches are
+maintained.
+.IP \(bu 2
+In earlier versions, only the batch order is maintained; document
+order within batches are not maintained.
+.UNINDENT
+.sp
+Starting in MongoDB 4.2,
+specifying \fI\%\-\-maintainInsertionOrder\fP also enables \fI\%\-\-stopOnError\fP and sets
+\fI\%numInsertionWorkersPerCollection\fP to 1.
+.sp
+If unspecified, \fBmongorestore\fP may perform the insertions in an
+arbitrary order.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-numParallelCollections int, \-j int
+.B \-\-numParallelCollections=<int>, \-j=<int>
 \fIDefault\fP: 4
 .sp
 Number of collections \fBmongorestore\fP should restore
@@ -1081,7 +1169,7 @@ maps to the \fI\%\-\-numInsertionWorkersPerCollection\fP option rather than
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-numInsertionWorkersPerCollection int
+.B \-\-numInsertionWorkersPerCollection=<int>
 \fIDefault\fP: 1
 .sp
 New in version 3.0.0.
@@ -1100,6 +1188,10 @@ New in version 3.0.
 .sp
 Forces \fBmongorestore\fP to halt the restore when it encounters an
 error.
+.sp
+Starting in version 4.2, \fI\%mongorestore\fP, by default,
+continues when it encounters duplicate key and document
+validation errors.  To ensure that the program stops on these errors, specify \fI\%\-\-stopOnError\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -1128,17 +1220,20 @@ both the \fI\%\-\-gzip\fP  and the \fI\-\-archive\fP options.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-archive <=file|null>
+.B \-\-archive=<file>
 New in version 3.2.
 
 .sp
-Restores from an archive file or from the standard input (\fBstdin\fP).
-.sp
-To restore from an archive file, run \fBmongorestore\fP with the \fB\-\-archive\fP
-option and the archive filename.
-.sp
-To restore from the standard input, run \fBmongorestore\fP with the
-\fB\-\-archive\fP option but \fIomit\fP the filename.
+Restores from the specified archive file or, if the file is
+unspecified, from the standard input (\fBstdin\fP):
+.INDENT 7.0
+.IP \(bu 2
+To restore from an archive file, run \fBmongorestore\fP with
+the \fB\-\-archive\fP option and the archive filename
+.IP \(bu 2
+To restore from the standard input, run \fBmongorestore\fP
+with the \fB\-\-archive\fP option but \fIomit\fP the filename.
+.UNINDENT
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
@@ -1173,7 +1268,7 @@ option, which also specifies the dump directory, to \fBmongorestore\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-dir string
+.B \-\-dir=string
 Specifies the dump directory.
 .INDENT 7.0
 .IP \(bu 2
@@ -1197,7 +1292,7 @@ prompt for the password.
 .sp
 .nf
 .ft C
-mongorestore \-\-uri "mongodb://user@mongodb1.example.net:27017/?authSource=admin" /opt/backup/mongodump\-2011\-10\-24
+mongorestore \-\-uri="mongodb://user@mongodb1.example.net:27017/?authSource=admin" /opt/backup/mongodump\-2011\-10\-24
 .ft P
 .fi
 .UNINDENT
@@ -1211,7 +1306,7 @@ authentication database using \fI\%\-\-host\fP,
 .sp
 .nf
 .ft C
-mongorestore \-\-host mongodb1.example.net \-\-port 27017 \-\-username user \-\-authenticationDatabase=admin /opt/backup/mongodump\-2011\-10\-24
+mongorestore \-\-host=mongodb1.example.net \-\-port=27017 \-\-username=user \-\-authenticationDatabase=admin /opt/backup/mongodump\-2011\-10\-24
 .ft P
 .fi
 .UNINDENT
@@ -1232,7 +1327,7 @@ files located in the \fBdump/\fP directory.
 .sp
 .nf
 .ft C
-mongorestore \-\-nsInclude test.purchaseorders dump/
+mongorestore \-\-nsInclude=test.purchaseorders dump/
 .ft P
 .fi
 .UNINDENT
@@ -1263,8 +1358,8 @@ files for the specified namespace, no data will be restored:
 .sp
 .nf
 .ft C
-2019\-07\-08T14:39:57.121\-0400 preparing collections to restore from
-2019\-07\-08T14:39:57.121\-0400 0 document(s) restored successfully. 0 document(s) failed to restore.
+2019\-07\-08T14:39:57.121\-0400. preparing collections to restore from
+2019\-07\-08T14:39:57.121\-0400  0 document(s) restored successfully. 0 document(s) failed to restore.
 .ft P
 .fi
 .UNINDENT
@@ -1277,7 +1372,7 @@ Alternatively, you can restore a specific collection using the
 .sp
 .nf
 .ft C
-mongorestore \-\-db test \-\-collection purchaseorders dump/test/purchaseorders.bson
+mongorestore \-\-db=test \-\-collection=purchaseorders dump/test/purchaseorders.bson
 .ft P
 .fi
 .UNINDENT
@@ -1321,7 +1416,7 @@ on port \fB27017\fP\&.
 .sp
 .nf
 .ft C
-mongorestore \-\-nsInclude \(aqtransactions.*\(aq \-\-nsExclude \(aqtransactions.*_dev\(aq dump/
+mongorestore \-\-nsInclude=\(aqtransactions.*\(aq \-\-nsExclude=\(aqtransactions.*_dev\(aq dump/
 .ft P
 .fi
 .UNINDENT
@@ -1372,7 +1467,7 @@ collections in the \fB<customerName>\fP database.
 .sp
 .nf
 .ft C
-mongorestore \-\-nsInclude \(aqdata.*\(aq \-\-nsFrom \(aqdata.$prefix$_$customer$\(aq \-\-nsTo \(aq$customer$.$prefix$\(aq
+mongorestore \-\-nsInclude=\(aqdata.*\(aq \-\-nsFrom=\(aqdata.$prefix$_$customer$\(aq \-\-nsTo=\(aq$customer$.$prefix$\(aq
 .ft P
 .fi
 .UNINDENT
@@ -1405,7 +1500,7 @@ following operation restores the \fBtest\fP database from the file
 .sp
 .nf
 .ft C
-mongorestore \-\-archive=test.20150715.archive  \-\-nsInclude "test.*"
+mongorestore \-\-archive=test.20150715.archive  \-\-nsInclude="test.*"
 .ft P
 .fi
 .UNINDENT
@@ -1425,7 +1520,7 @@ directory:
 .sp
 .nf
 .ft C
-mongorestore \-\-gzip  \-\-nsInclude "test.*" dump/
+mongorestore \-\-gzip  \-\-nsInclude="test.*" dump/
 .ft P
 .fi
 .UNINDENT
@@ -1440,7 +1535,7 @@ database from the archive file \fBtest.20150715.gz\fP\&.
 .sp
 .nf
 .ft C
-mongorestore \-\-gzip \-\-archive=test.20150715.gz \-\-nsInclude "test.*"
+mongorestore \-\-gzip \-\-archive=test.20150715.gz \-\-nsInclude="test.*"
 .ft P
 .fi
 .UNINDENT
@@ -1458,7 +1553,7 @@ the filename. For example:
 .sp
 .nf
 .ft C
-mongodump \-\-archive \-\-db test \-\-port 27017 | mongorestore \-\-archive \-\-port 27018
+mongodump \-\-archive \-\-db=test \-\-port=27017 | mongorestore \-\-archive \-\-port=27018
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongos.1 b/debian/mongos.1
index f1a5c14f9b6..e598179d0cb 100644
--- a/debian/mongos.1
+++ b/debian/mongos.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOS" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOS" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongos \- MongoDB Sharded Cluster Query Router
 .
@@ -524,11 +524,33 @@ _
 .INDENT 0.0
 .TP
 .B \-\-pidfilepath <path>
-Specifies a file location to hold the process ID of the \fBmongos\fP
-process where \fBmongos\fP will write its PID. This is useful for
-tracking the \fBmongos\fP process in combination with
-the \fI\%\-\-fork\fP option. Without a specified \fI\%\-\-pidfilepath\fP option, the
-process creates no PID file.
+Specifies a file location to store the process ID (PID) of the \fBmongos\fP
+process . The user running the the \fBmongod\fP or \fBmongos\fP
+process must be able to write to this path. If the \fI\%\-\-pidfilepath\fP option is not
+specified, the process does not create a PID file. This option is generally
+only useful in combination with the the \fI\%\-\-fork\fP option.
+.INDENT 7.0
+.INDENT 3.5
+.IP "Linux"
+.sp
+On Linux, PID file management is generally the responsibility of
+your distro\(aqs init system: usually a service file in the \fB/etc/init.d\fP
+directory, or a systemd unit file registered with \fBsystemctl\fP\&. Only
+use the \fI\%\-\-pidfilepath\fP option if you are not using one of these init
+systems. For more information, please see the respective
+Installation Guide for your operating system.
+.UNINDENT
+.UNINDENT
+.INDENT 7.0
+.INDENT 3.5
+.IP "macOS"
+.sp
+On macOS, PID file management is generally handled by \fBbrew\fP\&. Only use
+the \fI\%\-\-pidfilepath\fP option if you are not using \fBbrew\fP on your macOS system.
+For more information, please see the respective
+Installation Guide for your operating system.
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -622,6 +644,8 @@ background. By default \fBmongos\fP does not run as a daemon:
 typically you will run \fBmongos\fP as a daemon, either by using
 \fI\%\-\-fork\fP or by using a controlling process that handles the
 daemonization process (e.g. as with \fBupstart\fP and \fBsystemd\fP).
+.sp
+The \fI\%\-\-fork\fP option is not supported on Windows.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -791,12 +815,26 @@ mongos \-\-timeZoneInfo timezonedb\-2017b/
 New in version 4.2.
 
 .sp
-Outputs the resolved YAML configuration document for the \fBmongos\fP
-to \fBstdout\fP and halts the \fBmongos\fP instance. For configuration
-options using externally\-sourced\-values, \fI\%\-\-outputConfig\fP returns the
-resolved value for those options. This may include any configured
-passwords or secrets previously obfuscated through the external
-source.
+Outputs the \fBmongos\fP instance\(aqs configuration options, formatted
+in YAML, to \fBstdout\fP and exits the \fBmongos\fP instance. For
+configuration options that uses externally\-sourced\-values,
+\fI\%\-\-outputConfig\fP returns the resolved value for those options.
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+This may include any configured passwords or secrets previously
+obfuscated through the external source.
+.UNINDENT
+.UNINDENT
+.sp
+For usage examples, see:
+.INDENT 7.0
+.IP \(bu 2
+expansion\-directive\-output
+.IP \(bu 2
+/tutorial/convert\-command\-line\-options\-to\-yaml
+.UNINDENT
 .UNINDENT
 .SS Sharded Cluster Options
 .INDENT 0.0
@@ -2153,14 +2191,14 @@ New in version 4.0.
 New in version 3.4: Available in MongoDB Enterprise only.
 
 .sp
-The LDAP server against which the \fBmongos\fP executes LDAP operations
-against to authenticate users or determine what actions a user is authorized
-to perform on a given database. If the LDAP server specified has any
-replicated instances, you may specify the host and port of each replicated
-server in a comma\-delimited list.
+The LDAP server against which the \fBmongos\fP authenticates users or
+determines what actions a user is authorized to perform on a given
+database. If the LDAP server specified has any replicated instances,
+you may specify the host and port of each replicated server in a
+comma\-delimited list.
 .sp
-If your LDAP infrastrucure partitions the LDAP directory over multiple LDAP
-servers, specify \fIone\fP LDAP server any of its replicated instances to
+If your LDAP infrastructure partitions the LDAP directory over multiple LDAP
+servers, specify \fIone\fP LDAP server or any of its replicated instances to
 \fI\%\-\-ldapServers\fP\&. MongoDB supports following LDAP referrals as defined in \fI\%RFC 4511
 4.1.10\fP\&. Do not use \fI\%\-\-ldapServers\fP
 for listing every LDAP server in your infrastructure.
diff --git a/debian/mongostat.1 b/debian/mongostat.1
index 4cda514a21d..3cfc544ebf7 100644
--- a/debian/mongostat.1
+++ b/debian/mongostat.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOSTAT" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOSTAT" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongostat \- MongoDB Use Statistics
 .
@@ -35,6 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Synopsis\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
 \fI\%Required Access\fP
 .IP \(bu 2
 \fI\%Behavior\fP
@@ -65,6 +67,28 @@ UNIX/Linux file system utility \fBvmstat\fP, but provides data regarding
 \fBmongod\fP and \fBmongos\fP instances.
 .sp
 Run \fI\%mongostat\fP from the system command line, not the \fBmongo\fP shell.
+.SH AVAILABILITY
+.sp
+The \fI\%mongostat\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
 .SH REQUIRED ACCESS
 .sp
 In order to connect to a \fBmongod\fP that enforces authorization
@@ -108,7 +132,7 @@ Returns the \fBmongostat\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -119,7 +143,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -165,7 +189,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>, \-h <hostname><:port>
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
 \fIDefault\fP: localhost:27017
 .sp
 Specifies a resolvable hostname for the \fBmongod\fP to which to
@@ -180,7 +204,7 @@ members to report on, as in the following (see also the
 .sp
 .nf
 .ft C
-\-\-host <hostname1><:port>,<hostname2><:port>,<...>
+\-\-host=<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
@@ -200,7 +224,7 @@ You cannot specify both \fI\%\-\-host\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -238,7 +262,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -279,7 +303,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -298,18 +322,20 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
 Specifies the password to de\-crypt the certificate\-key file (i.e.
-\fI\%\-\-sslPEMKeyFile\fP). Use the \fI\%\-\-sslPEMKeyPassword\fP option only if the
-certificate\-key file is encrypted. In all cases, the \fBmongostat\fP will
-redact the password from all logging and reporting output.
+\fI\%\-\-sslPEMKeyFile\fP). Use the
+\fI\%\-\-sslPEMKeyPassword\fP option
+only if the certificate\-key file is encrypted. In all cases, the
+\fBmongostat\fP will redact the password from all logging and
+reporting output.
 .sp
-If the private key in the PEM file is encrypted and you do not specify
-the \fI\%\-\-sslPEMKeyPassword\fP option, the \fBmongostat\fP will prompt for a passphrase. See
-ssl\-certificate\-password\&.
+If the private key in the PEM file is encrypted and you do not
+specify the \fI\%\-\-sslPEMKeyPassword\fP option, the \fBmongostat\fP will prompt
+for a passphrase. See ssl\-certificate\-password\&.
 .sp
 For more information about TLS/SSL and MongoDB, see
 /tutorial/configure\-ssl and
@@ -317,7 +343,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -349,8 +375,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -393,9 +417,10 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
-Specifies a username with which to authenticate to a MongoDB database
-that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
+.B \-\-username=<username>, \-u=<username>
+Specifies a username with which to authenticate to a MongoDB
+database that uses authentication. Use in conjunction with the
+\fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
 .sp
 \fBNOTE:\fP
@@ -407,15 +432,15 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
-Specifies a password with which to authenticate to a MongoDB database
-that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
+.B \-\-password=<password>, \-p=<password>
+Specifies a password with which to authenticate to a MongoDB
+database that uses authentication. Use in conjunction with the
+\fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
 .sp
-Changed in version 3.0.2: To prompt the user
-for the password, pass the \fI\%\-\-username\fP option without
-\fI\%\-\-password\fP or specify an empty string as the \fI\%\-\-password\fP value,
-as in \fB\-\-password ""\fP .
+Changed in version 3.0.2: To prompt the user for the password, pass the \fI\%\-\-username\fP option without \fI\%\-\-password\fP or
+specify an empty string as the \fI\%\-\-password\fP value, as in
+\fB\-\-password=""\fP .
 
 .sp
 \fBNOTE:\fP
@@ -427,9 +452,10 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
-Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
-See user\-authentication\-database\&.
+.B \-\-authenticationDatabase=<dbname>
+Specifies the authentication database where the specified
+\fI\%\-\-username\fP has been created. See
+user\-authentication\-database\&.
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
@@ -443,7 +469,7 @@ and \fBmongos\fP instances that use authentication\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongostat\fP instance uses to
@@ -518,7 +544,7 @@ You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiServiceName
+.B \-\-gssapiServiceName=<string>
 New in version 2.6.
 
 .sp
@@ -529,7 +555,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiHostName
+.B \-\-gssapiHostName=<string>
 New in version 2.6.
 
 .sp
@@ -540,7 +566,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-humanReadable boolean
+.B \-\-humanReadable=<boolean>
 \fIDefault\fP: True
 .sp
 New in version 3.4.
@@ -582,7 +608,7 @@ insert query update delete getmore command dirty used flushes      vsize       r
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-o <field list>
+.B \-o=<field list>
 New in version 3.4.
 
 .sp
@@ -600,7 +626,7 @@ as in:
 .sp
 .nf
 .ft C
-mongostat \-o \(aqhost=H,time=T,version=MongoDB Version\(aq
+mongostat \-o=\(aqhost=H,time=T,version=MongoDB Version\(aq
 .ft P
 .fi
 .UNINDENT
@@ -639,7 +665,7 @@ See \fI\%Specify mongostat Output Fields\fP for an example of
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-O <field list>
+.B \-O=<field list>
 New in version 3.4.
 
 .sp
@@ -657,14 +683,14 @@ as in:
 .sp
 .nf
 .ft C
-mongostat \-O host=H,time=T
+mongostat \-O=host=H,time=T
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fBmongostat\fP supports specifying \fIeither\fP \fI\%\-O\fP or \fI\%\-o\fP:
-you cannot include both options.
+\fBmongostat\fP supports specifying \fIeither\fP \fI\%\-O\fP or \fI\%\-o\fP: you cannot include
+both options.
 .sp
 See \fI\%Add Fields to mongostat Output\fP for an example of
 \fI\%\-O\fP\&.
@@ -676,7 +702,7 @@ Disables the output of column or field names.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-rowcount <number>, \-n <number>
+.B \-\-rowcount=<number>, \-n=<number>
 Controls the number of rows to output. Use in conjunction with
 the \fBsleeptime\fP argument to control the duration of a
 \fI\%mongostat\fP operation.
@@ -959,10 +985,10 @@ behavior:
 .sp
 .nf
 .ft C
-mongostat \-\-rowcount 20 1
-mongostat \-\-rowcount 20
-mongostat \-n 20 1
-mongostat \-n 20
+mongostat \-\-rowcount=20 1
+mongostat \-\-rowcount=20
+mongostat \-n=20 1
+mongostat \-n=20
 .ft P
 .fi
 .UNINDENT
@@ -978,8 +1004,8 @@ invocations produce identical behavior:
 .sp
 .nf
 .ft C
-mongostat \-\-rowcount 0 300
-mongostat \-n 0 300
+mongostat \-\-rowcount=0 300
+mongostat \-n=0 300
 mongostat 300
 .ft P
 .fi
@@ -996,8 +1022,8 @@ behavior:
 .sp
 .nf
 .ft C
-mongostat \-\-rowcount 12 300
-mongostat \-n 12 300
+mongostat \-\-rowcount=12 300
+mongostat \-n=12 300
 .ft P
 .fi
 .UNINDENT
@@ -1018,7 +1044,7 @@ which will display as "network requests", to the default
 .sp
 .nf
 .ft C
-mongostat \-O \(aqhost,version,network.numRequests=network requests\(aq
+mongostat \-O=\(aqhost,version,network.numRequests=network requests\(aq
 .ft P
 .fi
 .UNINDENT
@@ -1052,7 +1078,7 @@ output. You can specify any \fBserverStatus\fP field as a
 .sp
 .nf
 .ft C
-mongostat \-o \(aqhost,time,metrics.document.inserted\(aq
+mongostat \-o=\(aqhost,time,metrics.document.inserted\(aq
 .ft P
 .fi
 .UNINDENT
@@ -1094,7 +1120,7 @@ to label \fBmetrics.document.inserted.rate()\fP as "inserted rate" and
 .sp
 .nf
 .ft C
-mongostat \-o \(aqhost,mem,bits,metrics.document.inserted.rate()=inserted rate,metrics.document.inserted=inserted\(aq \-\-rowcount 5
+mongostat \-o=\(aqhost,mem,bits,metrics.document.inserted.rate()=inserted rate,metrics.document.inserted=inserted\(aq \-\-rowcount=5
 .ft P
 .fi
 .UNINDENT
@@ -1134,7 +1160,7 @@ calls, while \fBinserted\fP is the value of
 .sp
 .nf
 .ft C
-mongostat \-o \(aqhost,mem.bits,metrics.document.inserted.diff()=inserted diff,metrics.document.inserted=inserted\(aq \-\-rowcount 5
+mongostat \-o=\(aqhost,mem.bits,metrics.document.inserted.diff()=inserted diff,metrics.document.inserted=inserted\(aq \-\-rowcount=5
 .ft P
 .fi
 .UNINDENT
diff --git a/debian/mongotop.1 b/debian/mongotop.1
index 23eb81c26bb..d9d8f842942 100644
--- a/debian/mongotop.1
+++ b/debian/mongotop.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "MONGOTOP" "1" "Jul 25, 2019" "4.2" "mongodb-manual"
+.TH "MONGOTOP" "1" "Oct 29, 2019" "4.2" "mongodb-manual"
 .SH NAME
 mongotop \- MongoDB Activity Monitor
 .
@@ -35,6 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fI\%Description\fP
 .IP \(bu 2
+\fI\%Availability\fP
+.IP \(bu 2
 \fI\%Syntax\fP
 .IP \(bu 2
 \fI\%Required Access\fP
@@ -65,6 +67,28 @@ MongoDB instance \fBmongod\fP spends reading and writing data.
 By default, \fI\%mongotop\fP returns values every second.
 .sp
 Run \fI\%mongotop\fP from the system command line, not the \fBmongo\fP shell.
+.SH AVAILABILITY
+.sp
+The \fI\%mongotop\fP tool is part of the MongoDB tools package. Consult the
+installation guide for your platform for
+instructions on how to install the tools package as part of your
+MongoDB installation.
+.sp
+The tools package is also available from the
+\fI\%MongoDB Download Center\fP,
+either as a separate \fBtools\fP download, or contained within the
+\fBTGZ\fP or \fBZIP\fP downloads, depending on platform. On Windows, the \fBMSI\fP installer includes all tools as part of the default installation.
+.INDENT 0.0
+.INDENT 3.5
+.SH TIP
+.sp
+If downloading the \fBTGZ\fP or \fBZIP\fP files from the Download
+Center, you may want to update your \fBPATH\fP environment
+variable to include the directory where you installed these tools.
+See the installation guide
+for your platform for more information.
+.UNINDENT
+.UNINDENT
 .SH SYNTAX
 .SS Default
 .INDENT 0.0
@@ -151,7 +175,7 @@ option to specify the host and port:
 .sp
 .nf
 .ft C
-mongotop 30 \-\-uri mongodb://mongodb0.example.com:27017 [additional options]
+mongotop 30 \-\-uri=\(aqmongodb://mongodb0.example.com:27017\(aq [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -165,7 +189,7 @@ of the URI connection string:
 .sp
 .nf
 .ft C
-mongotop 30 \-\-uri mongodb://user:password@mongodb0.example.com:27017/?authSource=admin [additional options]
+mongotop 30 \-\-uri=\(aqmongodb://user:password@mongodb0.example.com:27017/?authSource=admin\(aq [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -185,22 +209,22 @@ and port:
 .sp
 .nf
 .ft C
-mongotop 30 \-\-host mongodb0.example.com \-\-port 27017 [additional options]
+mongotop 30 \-\-host=mongodb0.example.com \-\-port=27017 [additional options]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
 If the \fBmongod\fP instance requires authentication, you
-can specify the user \fI\%\-u\fP, password
-\fI\%\-p\fP, and the authentication database
-\fI\%\-\-authenticationDatabase\fP\&.
+can specify the user \fI\%\-u\fP, and the
+authentication database \fI\%\-\-authenticationDatabase\fP\&. Omit the \fI\%\-\-password\fP option to have \fBmongoexport\fP prompt for the
+password.
 .INDENT 2.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-mongotop 30 \-\-host mongodb0.example.com \-\-port 27017 \-u user \-p password \-\-authenticationDatabase admin [additional options]
+mongotop 30 \-\-host=mongodb0.example.com \-\-port=27017 \-u=user \-\-authenticationDatabase=admin [additional options]
 .ft P
 .fi
 .UNINDENT
@@ -288,7 +312,7 @@ Returns the \fBmongotop\fP release number.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-uri <connectionString>
+.B \-\-uri=<connectionString>
 New in version 3.4.6.
 
 .sp
@@ -299,7 +323,7 @@ connection string (enclose in quotes) to connect to the MongoDB deployment.
 .sp
 .nf
 .ft C
-\-\-uri "mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+\-\-uri="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
 .ft P
 .fi
 .UNINDENT
@@ -345,7 +369,7 @@ connection string.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-host <hostname><:port>, \-h <hostname><:port>
+.B \-\-host=<hostname><:port>, \-h=<hostname><:port>
 \fIDefault\fP: localhost:27017
 .sp
 Specifies a resolvable hostname for the \fBmongod\fP to which to
@@ -360,7 +384,7 @@ the following:
 .sp
 .nf
 .ft C
-\-\-host <replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
+\-\-host=<replSetName>/<hostname1><:port>,<hostname2><:port>,<...>
 .ft P
 .fi
 .UNINDENT
@@ -376,7 +400,7 @@ the host and port of only that member:
 .sp
 .nf
 .ft C
-\-\-host <hostname1><:port>
+\-\-host=<hostname1><:port>
 .ft P
 .fi
 .UNINDENT
@@ -399,7 +423,7 @@ reachable, \fBmongotop\fP returns an error message.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-port <port>
+.B \-\-port=<port>
 \fIDefault\fP: 27017
 .sp
 Specifies the TCP port on which the MongoDB instance listens for
@@ -437,7 +461,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCAFile <filename>
+.B \-\-sslCAFile=<filename>
 New in version 2.6.
 
 .sp
@@ -478,7 +502,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyFile <filename>
+.B \-\-sslPEMKeyFile=<filename>
 New in version 2.6.
 
 .sp
@@ -497,7 +521,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslPEMKeyPassword <value>
+.B \-\-sslPEMKeyPassword=<value>
 New in version 2.6.
 
 .sp
@@ -516,7 +540,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-sslCRLFile <filename>
+.B \-\-sslCRLFile=<filename>
 New in version 2.6.
 
 .sp
@@ -548,8 +572,6 @@ authentication, an invalid certificate is only sufficient to
 establish a TLS/SSL connection but is \fIinsufficient\fP for
 authentication.
 .sp
-# We created a separate blurb for tls in the ssl\-clients page.
-.sp
 \fBWARNING:\fP
 .INDENT 7.0
 .INDENT 3.5
@@ -592,7 +614,7 @@ For more information about TLS/SSL and MongoDB, see
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-username <username>, \-u <username>
+.B \-\-username=<username>, \-u=<username>
 Specifies a username with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-password\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -606,7 +628,7 @@ You cannot specify both \fI\%\-\-username\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-password <password>, \-p <password>
+.B \-\-password=<password>, \-p=<password>
 Specifies a password with which to authenticate to a MongoDB database
 that uses authentication. Use in conjunction with the \fI\%\-\-username\fP and
 \fI\%\-\-authenticationDatabase\fP options.
@@ -626,7 +648,7 @@ You cannot specify both \fI\%\-\-password\fP and \fI\%\-\-uri\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationDatabase <dbname>
+.B \-\-authenticationDatabase=<dbname>
 Specifies the authentication database where the specified \fI\%\-\-username\fP has been created.
 See user\-authentication\-database\&.
 .sp
@@ -643,7 +665,7 @@ and \fBmongos\fP instances that use authentication\&.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-authenticationMechanism <name>
+.B \-\-authenticationMechanism=<name>
 \fIDefault\fP: SCRAM\-SHA\-1
 .sp
 Specifies the authentication mechanism the \fBmongotop\fP instance uses to
@@ -718,7 +740,7 @@ You cannot specify both \fI\%\-\-authenticationMechanism\fP and \fI\%\-\-uri\fP\
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiServiceName
+.B \-\-gssapiServiceName=<serviceName>
 New in version 2.6.
 
 .sp
@@ -729,7 +751,7 @@ This option is available only in MongoDB Enterprise.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-gssapiHostName
+.B \-\-gssapiHostName=<hostname>
 New in version 2.6.
 
 .sp
@@ -750,7 +772,7 @@ newer instance that does not report per\-database lock usage.
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-rowcount int, \-n int
+.B \-\-rowcount=<int>, \-n=<int>
 Number of lines of data that \fBmongotop\fP should print. "0 for indefinite"
 .UNINDENT
 .INDENT 0.0