[SERVER-47413] Some transaction tests are not being retried on Transient Error Created: 08/Apr/20  Updated: 15/Apr/20  Resolved: 15/Apr/20

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Tommaso Tocci
Resolution: Won't Do Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45781 Throw Stale Shard Version when collec... Closed
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
Sprint: Sharding 2020-04-20
Participants:

 Description   

As part of PM-1645 when trying to access the metadata of a collection, that is, the description or the ownership filter, if the metadata has not being loaded yet, the API can throw Stale Shard Version. In the case of the transactions, this is known as a Transient Error, and in general it must be handled by the client (with one exception). This means that some transaction tests will need to add a retrying, like this test. Some tests that needs to be changed are:



 Comments   
Comment by Tommaso Tocci [ 15/Apr/20 ]

We changed the approach to remove all the calls to getCollectionDescription_DEPRECATED, we will do this as part of SERVER-47521 and all its sub-tickets.
In particular the changes to:

  • jstests/core/txns/view_reads_in_transaction.js
  • src/mongo/db/commands/distinct.cpp

have been already introduced in SERVER-47522

Changes to:

  • jstests/core/txns/commands_in_txns_read_concern.js

will be introduced in SERVER-47524

We still need to decide if changes to:

  • jstests/core/txns/create_indexes_parallel.js
  • jstests/core/txns/create_indexes.js

Are still needed

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