[SERVER-36392] Make tests that rely on the autosplitter unintentially not require the autosplitter Created: 01/Aug/18  Updated: 29/Oct/23  Resolved: 09/Aug/18

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-08-13
Participants:

 Description   

Some tests like authCommands.js insert some documents and then call moveChunk, expecting the autosplitter to have run. With the new autosplitting behavior, splitting is asynchronous, so it won't necessarily have completed in between the inserts and the moveChunk, so the moveChunk will fail because the chunk will be too large. These tests are not intentionally testing this autosplitter behavior, so they shouldn't rely on it. In cases like these we should call the splitChunk command manually.



 Comments   
Comment by Githook User [ 09/Aug/18 ]

Author:

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

Message: SERVER-36392 Make tests that rely on the autosplitter unintentially not require the autosplitter
Branch: master
https://github.com/mongodb/mongo/commit/25de1e85f2369d00391979f6efc5827d5e574e6f

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