[DOCS-9534] Docs for SERVER-22671: Implement serverStatus section with active migrations Created: 05/Dec/16  Updated: 30/Oct/23  Resolved: 24/Mar/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Ravind Kumar (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-22671 Implement serverStatus section with a... Closed
Participants:
Days since reply: 45 weeks, 5 days ago

 Description   

Engineering Ticket Description:

Implement an optional serverStatus section, available both on the config server and on the shards, which returns information about all the active chunk migrations. This section will be used by support and possibly by the balancer when it resumes from primary stepdown.

On the shards, this serverStatus section should look like this (and should be placed under the optional sharding section):

sharding: {
	migrations: [
		{ source: ShardId,
                  sourceHost: Host:Port,
                  destination: ShardId,
                  destinationHost: Host:Port,
                  chunk: { min: <MinKey>, max: <MaxKey> },
                  phase: String, one of <INIT, CATCHUP, CRITICAL SECTION>,
		},
		...
	]
}

On the config server, the section should be the union of all migrations across all shards.



 Comments   
Comment by Sarah Olson [ 24/Mar/23 ]

Closing this out on the grounds that:

  • Details of this request are significantly outdated. 
  • Our documentation has evolved substantially since this request was made. 

Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree.

Generated at Thu Feb 08 07:58:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.