[DOCS-15536] Resharding Requirement Docs is too lax on what users can do to reshards Created: 11/Aug/22  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Garaudy Etienne Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, proactive, query, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 25 weeks, 6 days ago
Epic Link: DOCSP-11702

 Description   

https://www.mongodb.com/docs/manual/core/sharding-reshard-a-collection/

Current docs message:
"You must perform one of these tasks:

  • rewrite your application's queries to use both the current shard key and the new shard key
  • stop your application and then:
  • rewrite your application's queries to use the new shard key
  • wait until the resharding of the collection completes (to monitor the resharding process, use a $currentOp pipeline stage)
  • deploy your rewritten application"

The message should instead be:
"you must rewrite your application's queries to use both the current shard key and the new shard key.

tip
If you can afford some downtime, you can stop your application, rewrite your application to use the new shard key, wait until resharding completes, then deploy your rewritten application."



 Comments   
Comment by Garaudy Etienne [ 11/Aug/22 ]

max.hirschhorn@mongodb.com

Generated at Thu Feb 08 08:13:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.