[DOCS-8950] Sharding migration transfers all document deletions Created: 28/Sep/16  Updated: 30/Oct/23  Resolved: 20/Jul/17

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: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-21382 Sharding migration transfers all docu... Closed
Participants:
Days since reply: 6 years, 30 weeks ago
Epic Link: 3.4: Sharding Updates

 Description   

During chunk migration, the donor shard will record all document deletions and transfer them to the recipient, regardless of whether the deletions are relevant to the chunk being migrated or not.

This causes significant load on both shards.

The reason for this is that the document being deleted is no longer available on the donor shard.

One solution would be that in the logOp call we should pass the shard key of the document being deleted so it can be filtered out.



 Comments   
Comment by Kay Kim (Inactive) [ 20/Jul/17 ]

The server was updated to be not-needed.

Comment by Dianna Hohensee (Inactive) [ 29/Sep/16 ]

This is internal and nothing a user should know about.

ramon.fernandez, you set documentation needed on the original SERVER ticket. Do you agree?

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