@@ -219,13 +219,13 @@ asserts
219
219
A document that reports on the number of assertions raised since the
220
220
MongoDB process started. While assert errors are typically uncommon,
221
221
if there are non-zero values for the :data:`asserts`, you should
222
- check the log file for more information. In many cases, these errors
223
- are trivial, but are worth investigating.
222
+ examine the log file for more information. In many cases, these
223
+ errors are trivial, but are worth investigating.
224
224
225
225
.. serverstatus:: asserts.regular
226
226
227
227
The number of regular assertions raised since the MongoDB process
228
- started. Check the log file for more information about these
228
+ started. Examine the log file for more information about these
229
229
messages.
230
230
231
231
.. serverstatus:: asserts.warning
@@ -240,7 +240,7 @@ asserts
240
240
.. serverstatus:: asserts.msg
241
241
242
242
The number of message assertions raised since the MongoDB process
243
- started. Check the log file for more information about these
243
+ started. Examine the log file for more information about these
244
244
messages.
245
245
246
246
.. serverstatus:: asserts.user
@@ -249,7 +249,7 @@ asserts
249
249
the MongoDB process started. These are errors that user may
250
250
generate, such as out of disk space or duplicate key. You can
251
251
prevent these assertions by fixing a problem with your application
252
- or deployment. Check the MongoDB log for more information.
252
+ or deployment. Examine the MongoDB log for more information.
253
253
254
254
.. serverstatus:: asserts.rollovers
255
255
@@ -271,6 +271,7 @@ connections
271
271
"available" : <num>,
272
272
"totalCreated" : <num>,
273
273
"active" : <num>,
274
+ "threaded" : <num>,
274
275
"exhaustIsMaster" : <num>,
275
276
"awaitingTopologyChanges" : <num>
276
277
},
@@ -284,7 +285,7 @@ connections
284
285
.. serverstatus:: connections.current
285
286
286
287
The number of incoming connections from clients to the database
287
- server . This number includes the current shell session. Consider
288
+ server. This number includes the current shell session. Consider
288
289
the value of :serverstatus:`connections.available` to add more
289
290
context to this datum.
290
291
@@ -313,6 +314,13 @@ connections
313
314
314
315
.. versionadded:: 4.0.7
315
316
317
+ .. serverstatus:: connections.threaded
318
+
319
+ The number of incoming connections from clients that are assigned
320
+ to threads that service client requests.
321
+
322
+ .. versionadded:: 5.0
323
+
316
324
.. serverstatus:: connections.exhaustIsMaster
317
325
318
326
The number of connections whose last request was an
@@ -358,8 +366,7 @@ information.
358
366
359
367
.. serverstatus:: defaultRWConcern
360
368
361
- The last known global default read or write concern
362
- settings.
369
+ The last known global default read or write concern settings.
363
370
364
371
.. versionadded:: 4.4
365
372
@@ -429,12 +436,12 @@ information.
429
436
430
437
.. serverstatus:: defaultRWConcern.updateWallClockTime
431
438
432
- The wall clock time when the instance last updated its copy of
433
- any global read or write concern settings. If the
434
- :serverstatus:`defaultRWConcern.defaultReadConcern` and
435
- :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are
436
- absent, this field indicates the time when the
437
- defaults were last unset.
439
+ The wall clock time when the instance last updated its copy of any
440
+ global read or write concern settings. If the
441
+ :serverstatus:`defaultRWConcern.defaultReadConcern` and
442
+ :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are
443
+ absent, this field indicates the time when the defaults were last
444
+ unset.
438
445
439
446
.. versionadded:: 4.4
440
447
@@ -520,7 +527,7 @@ primary:
520
527
.. serverstatus:: electionMetrics.catchUpTakeover
521
528
522
529
Metrics on elections called by the :binary:`~bin.mongod` instance
523
- because it is more-up-to-date than the primary.
530
+ because it is more current than the primary.
524
531
525
532
The :serverstatus:`~electionMetrics.catchUpTakeover` includes both the number of
526
533
elections called and the number of elections that succeeded.
@@ -556,7 +563,7 @@ primary:
556
563
.. serverstatus:: electionMetrics.numStepDownsCausedByHigherTerm
557
564
558
565
Number of times the :binary:`~bin.mongod` instance stepped down
559
- because it saw a higher term (i.e. other member/members have
566
+ because it saw a higher term (specifically, other member(s)
560
567
participated in additional elections).
561
568
562
569
*Available starting in 4.2.1 (and 4.0.13)*
@@ -581,7 +588,7 @@ primary:
581
588
582
589
Number of times the :binary:`~bin.mongod` instance as the
583
590
newly-elected primary concluded its catchup process because it was
584
- already caught up when elected
591
+ already caught up when elected.
585
592
586
593
*Available starting in 4.2.1 (and 4.0.13)*
587
594
@@ -609,9 +616,9 @@ primary:
609
616
610
617
.. serverstatus:: electionMetrics.numCatchUpsFailedWithNewTerm
611
618
612
- Number of times the newly-elected primary's catchup process
613
- concluded because another member(s) had a higher term (i.e. other
614
- member/members have participated in additional elections).
619
+ Number of times the newly-elected primary's catchup process concluded
620
+ because another member(s) had a higher term (specifically, other
621
+ member(s) participated in additional elections).
615
622
616
623
*Available starting in 4.2.1 (and 4.0.13)*
617
624
@@ -647,8 +654,8 @@ extra_info
647
654
648
655
.. serverstatus:: extra_info
649
656
650
- A document that provides additional information regarding the
651
- underlying system.
657
+ A document that provides additional information about the underlying
658
+ system.
652
659
653
660
.. serverstatus:: extra_info.note
654
661
@@ -2871,7 +2878,7 @@ shardedIndexConsistency
2871
2878
collection does not have the exact same indexes (including the index
2872
2879
options) on each shard that contains chunks for the collection.
2873
2880
2874
- To check if a sharded collection has inconsistent indexes, see
2881
+ To investigate if a sharded collection has inconsistent indexes, see
2875
2882
:ref:`manage-indexes-find-inconsistent-indexes`.
2876
2883
2877
2884
The returned metrics are meaningful only when run on the primary of
@@ -4697,8 +4704,8 @@ metrics
4697
4704
4698
4705
.. serverstatus:: metrics.storage.freelist.search.bucketExhausted
4699
4706
4700
- The number of times that :binary:`~bin.mongod` has checked the free list
4701
- without finding a suitably large record allocation.
4707
+ The number of times that :binary:`~bin.mongod` has examined the free
4708
+ list without finding a suitably large record allocation.
4702
4709
4703
4710
.. serverstatus:: metrics.storage.freelist.search.requests
4704
4711
@@ -4800,8 +4807,9 @@ watchdog
4800
4807
4801
4808
.. serverstatus:: watchdog.monitorGeneration
4802
4809
4803
- The number of times the status of all filesystems used by :binary:`~bin.mongod`
4804
- has been checked. This is incremented once every ``monitoringPeriod``.
4810
+ The number of times the status of all filesystems used by
4811
+ :binary:`~bin.mongod` has been examined. This is incremented once
4812
+ every ``monitoringPeriod``.
4805
4813
4806
4814
.. serverstatus:: watchdog.monitorPeriod
4807
4815
0 commit comments