[SERVER-65113] Exclude resharding_disallow_writes.js from multiversion suites and revert callMod expected errors Created: 31/Mar/22  Updated: 29/Oct/23  Resolved: 31/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
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
Sprint: Sharding EMEA 2022-04-04
Participants:
Linked BF Score: 166

 Description   

The `resharding_disallow_writes.js` started failing after SERVER-64464 due to sanity checks added on shard versions.

It tests that some commands work as expected while resharding is in progress. In particular, the collMod command is expected to fail due to ReshardCollectionInProgress or MaxTimeMSExpired. This has been recently changed since just MaxTimeMSExpired was expected (as for the DDL operations) but this does work on multiversion suite.

As aggreed with max.hirschhorn, the gaol of this ticket is to revert the preciously expected errors for the collMod command and exclude this test from multiversion suite. Further analyzes will follow to better define expectations also in multiversion.



 Comments   
Comment by Githook User [ 31/Mar/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-65113 Exclude resharding_disallow_writes.js from multiversion suites and revert callMod expected errors
Branch: master
https://github.com/mongodb/mongo/commit/b1cf403753841ab2ea8e7d6bec145e52645d0070

Comment by Antonio Fuschetto [ 31/Mar/22 ]

After further discussion (see PR #4299), we decided to exclude this test from the multiversion suites. We will discuss more about the overall semantics for DDL operations attempted during a resharding operation without the pressure of fixing this hot BF ticket.

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