[SERVER-54442] Test that operation context does not keep aborted transaction metadata on step-up Created: 10/Feb/21  Updated: 29/Oct/23  Resolved: 15/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-52777 Fit 'refineShardKey' in the DDL coord... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

refine_collection_shard_key_abort_on_stepup.js is a regression test for SERVER-48527 to make sure that the operation context keeps no session metadata from transactions aborted as part of step-up.

Calling a refine shard key is an indirect way to test such behavior because it internally executes a transaction on the config server.

Under PM-1965, all DDL operations are being modified to happen under a distributed lock, causing trouble for the test expecting distributed locks to be not used. Moreover, the transaction is probably going to be emulated soon with a read at clusterTime in order to move the logic on the primary shard (there is currently no support for transaction on the CSRS from shards).

This ticket is to test in a more direct way (e.g. with a unit test) that transaction metadata are discarded from the operation context on step-up.



 Comments   
Comment by Githook User [ 11/Feb/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-54442 Test that operation context does not keep aborted transaction metadata on step-up
Branch: master
https://github.com/mongodb/mongo/commit/1b374e4188e9dcfd7499064afab451690268a748

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