@@ -2391,6 +2391,12 @@ repl
23912391 "primary" : <hostname>,
23922392 "me" : <hostname>,
23932393 "electionId" : ObjectId(""),
2394+ "primaryOnlyServices": {
2395+ "ReshardingRecipientService": { "state": <string>, "numInstances": <num> },
2396+ "RenameCollectionParticipantService": { "state": <string>, "numInstances": <num> },
2397+ "ShardingDDLCoordinator": { "state": <string>, "numInstances": <num> },
2398+ "ReshardingDonorService": { "state": <string>, "numInstances": <num> }
2399+ },
23942400 "rbid" : <num>,
23952401 "replicationProgress" : [
23962402 {
@@ -2441,6 +2447,76 @@ repl
24412447 The hostname and port information (``"host:port"``) for the current
24422448 member of the replica set.
24432449
2450+ .. serverstatus:: repl.primaryOnlyServices
2451+
2452+ Document that contains the number and status of
2453+ instances of each primary service active on the server. Primary
2454+ services can only start when a server is primary but can continue running to
2455+ completion after the server changes state.
2456+
2457+ .. versionadded:: 5.0
2458+
2459+ .. serverstatus:: repl.primaryOnlyServices.ReshardingRecipientService
2460+
2461+ Document that contains the state and number of instances of the
2462+ ``ReshardingRecipientService``.
2463+
2464+ Recipients are the shards,that would own the chunks after as a
2465+ result of the resharding operation, according to the new
2466+ :manual:`shard key</core/sharding-shard-key/>` and
2467+ :manual:`zones</core/zone-sharding/>`.
2468+
2469+ The resharding coordinator instructs each donor and recipient shard
2470+ primary, to rename the temporary sharded collection.
2471+ The temporary collection becomes the new resharded collection.
2472+
2473+ .. versionadded:: 5.0
2474+
2475+ .. serverstatus:: repl.primaryOnlyServices.RenameCollectionParticipantService
2476+
2477+ Document that contains the state and number of instances of the
2478+ ``RenameCollectionParticipantService``.
2479+
2480+ The ``RenameCollectionParticipantService`` ensures that, after a shard
2481+ receives a
2482+ :manual:`renameCollection</reference/method/db.collection.renameCollection/>`
2483+ request, the shard is able to resume the local rename in case of
2484+ system failure.
2485+
2486+ .. versionadded:: 5.0
2487+
2488+ .. serverstatus:: repl.primaryOnlyServices.ShardingDDLCoordinator
2489+
2490+ Document that contains the state and number of instances of the
2491+ ``ShardingDDLCoordinator``.
2492+
2493+ The ``ShardingDDLCoordinator`` service manages DDL operations for
2494+ :manual:`primary</core/replica-set-members/#std-label-replica-set-primary-member>`
2495+ databases such as:
2496+ :manual:`create database</core/databases-and-collections/#create-a-database>`,
2497+ :manual:`drop database</reference/method/db.dropDatabase/>`,
2498+ :manual:`renameCollection</reference/method/db.collection.renameCollection>`.
2499+
2500+ The ``ShardingDDLCoordinator`` ensures that one DDL operation for
2501+ each database can happen at any one specific point in time within a
2502+ sharded cluster.
2503+
2504+ .. versionadded:: 5.0
2505+
2506+ .. serverstatus:: repl.primaryOnlyServices.ReshardingDonorService
2507+
2508+ Document that contains the state and number of instances of the
2509+ ``ReshardingDonorService``.
2510+
2511+ Donors are the shards that own chunks of the sharded collection
2512+ before the rename operation completes.
2513+
2514+ The resharding coordinator instructs each donor and recipient shard
2515+ primary, to rename the temporary sharded collection.
2516+ The temporary collection becomes the new resharded collection.
2517+
2518+ .. versionadded:: 5.0
2519+
24442520.. serverstatus:: repl.rbid
24452521
24462522 :term:`Rollback <rollback>` identifier. Used to determine if a rollback has
0 commit comments