[SERVER-43397] Blacklist FSM workloads that perform multi-deletes from balancer and migration suites. Created: 20/Sep/19  Updated: 29/Oct/23  Resolved: 23/Sep/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-10-07
Participants:
Linked BF Score: 19

 Description   

Workloads that perform multi-deletes and then assert on the number of documents deleted will not work with balancer or migration suites. This is because multi-deletes aren't versioned, and thus do not filter for orphans. During and after migrations, there could exist an undefined number of orphans, due to either:

  1. Documents currently streaming to the current node in process of a migration that have not yet been "assigned" to the node via shard versioning, or
  2. Documents not yet deleted ("left over") on a node that has officially migrated documents to another node.

The consistent solution is to blacklist these suites from the balancer and migration suites.



 Comments   
Comment by Githook User [ 23/Sep/19 ]

Author:

{'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz'}

Message: SERVER-43397 Blacklist FSM workloads that perform multi-deletes from balancer and migration suites
Branch: master
https://github.com/mongodb/mongo/commit/89f0a9ab0b0328937ceeb9af5f55566421447759

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