[SERVER-72359] Cleanup `onConcurrentShardSince` in `sharded_backup_restore.js` Created: 22/Dec/22  Updated: 29/Oct/23  Resolved: 22/Dec/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Silvia Surroca
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 EMEA 2022-12-26
Participants:
Linked BF Score: 161

 Description   

The sharded_backup_restore.js test is simulating a restore of a sharded cluster, resetting the history when the chunks are moved on a new cluster:

            assert.commandWorked(configDb.chunks.update(
                {shard: sourceShardName}, {$set: {shard: destShardName, history: []}}));

Since the field added under SERVER-71615 always need to be consistent with the first element of the history, the test needs to be changed in order to also clear up that field.



 Comments   
Comment by Githook User [ 22/Dec/22 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-72359 Cleanup onConcurrentShardSince in sharded_backup_restore.js
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/208ebaba34fbceddd5032ca338676058e6f1ae60

Generated at Thu Feb 08 06:21:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.