diff --git a/source/reference/command/serverStatus.txt b/source/reference/command/serverStatus.txt index c131d2c8379..9827cac2c2b 100644 --- a/source/reference/command/serverStatus.txt +++ b/source/reference/command/serverStatus.txt @@ -2391,6 +2391,12 @@ repl "primary" : , "me" : , "electionId" : ObjectId(""), + "primaryOnlyServices": { + "ReshardingRecipientService": { "state": , "numInstances": }, + "RenameCollectionParticipantService": { "state": , "numInstances": }, + "ShardingDDLCoordinator": { "state": , "numInstances": }, + "ReshardingDonorService": { "state": , "numInstances": } + }, "rbid" : , "replicationProgress" : [ { @@ -2441,6 +2447,76 @@ repl The hostname and port information (``"host:port"``) for the current member of the replica set. +.. serverstatus:: repl.primaryOnlyServices + + Document that contains the number and status of + instances of each primary service active on the server. Primary + services can only start when a server is primary but can continue running to + completion after the server changes state. + + .. versionadded:: 5.0 + +.. serverstatus:: repl.primaryOnlyServices.ReshardingRecipientService + + Document that contains the state and number of instances of the + ``ReshardingRecipientService``. + + Recipients are the shards,that would own the chunks after as a + result of the resharding operation, according to the new + :manual:`shard key` and + :manual:`zones`. + + The resharding coordinator instructs each donor and recipient shard + primary, to rename the temporary sharded collection. + The temporary collection becomes the new resharded collection. + + .. versionadded:: 5.0 + +.. serverstatus:: repl.primaryOnlyServices.RenameCollectionParticipantService + + Document that contains the state and number of instances of the + ``RenameCollectionParticipantService``. + + The ``RenameCollectionParticipantService`` ensures that, after a shard + receives a + :manual:`renameCollection` + request, the shard is able to resume the local rename in case of + system failure. + + .. versionadded:: 5.0 + +.. serverstatus:: repl.primaryOnlyServices.ShardingDDLCoordinator + + Document that contains the state and number of instances of the + ``ShardingDDLCoordinator``. + + The ``ShardingDDLCoordinator`` service manages DDL operations for + :manual:`primary` + databases such as: + :manual:`create database`, + :manual:`drop database`, + :manual:`renameCollection`. + + The ``ShardingDDLCoordinator`` ensures that one DDL operation for + each database can happen at any one specific point in time within a + sharded cluster. + + .. versionadded:: 5.0 + +.. serverstatus:: repl.primaryOnlyServices.ReshardingDonorService + + Document that contains the state and number of instances of the + ``ReshardingDonorService``. + + Donors are the shards that own chunks of the sharded collection + before the rename operation completes. + + The resharding coordinator instructs each donor and recipient shard + primary, to rename the temporary sharded collection. + The temporary collection becomes the new resharded collection. + + .. versionadded:: 5.0 + .. serverstatus:: repl.rbid :term:`Rollback ` identifier. Used to determine if a rollback has diff --git a/source/release-notes/5.0.txt b/source/release-notes/5.0.txt index 5d185a7d151..9a9a0b24198 100644 --- a/source/release-notes/5.0.txt +++ b/source/release-notes/5.0.txt @@ -909,6 +909,13 @@ Security Counter which reports the number of times a :dbcommand:`hello` request includes a valid :data:`hello.saslSupportedMechs` field. +Repl + - :serverstatus:`repl` now includes a + :serverstatus:`~repl.primaryOnlyServices` document that + contains additional information about services that only run on + replica set primaries. + + Plan Cache Debug Info Size Limit ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~