[SERVER-41084] Manually ensure that orphaned documents exist on document shard key test Created: 10/May/19  Updated: 29/Oct/23  Resolved: 14/May/19

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

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
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-05-20
Participants:
Linked BF Score: 11

 Description   

In this document shard key test, we rely on orphans existing after a chunk has been moved. If the orphans end up getting deleted by the range deleter, then the test will fail. We should manually ensure that orphaned documents exist, in case the range deleter has ran.



 Comments   
Comment by Githook User [ 14/May/19 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-41084 Manually insert orphan to test duplicate key errors when changing document shard key
Branch: master
https://github.com/mongodb/mongo/commit/441a12bb63f26eb8afa54be270707234f6f4591d

Generated at Thu Feb 08 04:56:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.