[DOCS-11680] [Server] Update Migration Thresholds for MongoDB 3.4 or above Created: 09/May/18  Updated: 08/Jan/24  Resolved: 20/Nov/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.4 Required, 5.0 Required, Server_Docs_[20240108]

Type: Task Priority: Major - P3
Reporter: Linda Qin Assignee: Lauren Tran
Resolution: Done Votes: 0
Labels: reopened, server-docs-bug-bash, sharding, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 12 weeks, 5 days ago
Story Points: 2

 Description   

Triage notes: it looks like the only doc change is here: https://docs.mongodb.com/manual/core/sharding-balancer-administration/index.html#migration-thresholds.

Also, "migration thresholds" links to itself on this page. Does it make sense to explain this further?

 

Document Migration Thresholds:

  • In MongoDB 3.2 or earlier, the migration thresholds are calculated by difference in number of chunks between the shard with the most chunks for the collection and the shard with the fewest chunks for that collection.
  • However, the migration thresholds have been changed since MongoDB 3.4 in SERVER-24721, and also 4.0 in SERVER-35003. We'd need to update the document on the migration thresholds for MongoDB 3.4 or above.


 Comments   
Comment by Lauren Tran [ 10/Nov/23 ]

garaudy.etienne@mongodb.com it is currently in external review and pierlauro.sciarelli@mongodb.com said he will review it next week!

Comment by Garaudy Etienne [ 10/Nov/23 ]

lauren.tran@mongodb.com did we ever finish this ticket?

Comment by Ashley Brown [ 12/May/23 ]

Thanks matt.panton@mongodb.com and pierlauro.sciarelli@mongodb.com! Who would be the best person for a technical review once this change is drafted?

Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Randolph Tan [ 02/Jan/20 ]

Was it because they were having more migrations than before? If not, the CPU usage might be caused by something else.

Comment by Siyuan Zhou [ 01/Jan/20 ]

A user in Chineses community noticed this disparity since they observed the CPU usage of a hash sharded cluster increased from 10% to 40% after upgrading from 3.6 to 4.0. CC renctan.

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