[SERVER-47835] Un-blacklist txn_passthrough_runner_selftest.js system.profile read Created: 29/Apr/20  Updated: 21/Jun/23  Resolved: 19/Jun/23

Status: Closed
Project: Core Server
Component/s: Shell, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: sdp-backlog-purge
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-78266 Complete TODO listed in SERVER-47835 Closed
is related to SERVER-46900 Prohibit operations on system.profile... Closed
Assigned Teams:
Server Development Platform
Operating System: ALL
Backport Requested:
v4.4
Participants:

 Description   

As of SERVER-33548, when profiling is enabled, we expect profile writes for operations inside of transactions to appear in system.profile independently of whether the transaction commits. This transactions override test asserts that the operations are not visible in system.profile, and seems to have been passing because of visibility rules for reads inside transactions (see my comment).

As of SERVER-46900, it's not possible to read from system.profile inside of a transaction. Upon modifying the transactions override framework to not run the read to system.profile inside of a transaction, the jstests/libs/txns/txn_passthrough_runner_selftest.js fails because this read returns nonempty results, as expected.

SERVER-46900 will blacklist the offending find and any other dependent portions in the test.



 Comments   
Comment by Alex Neben [ 19/Jun/23 ]

This has been identified as work that the SDP team won't do in the near term. Please reopen with a comment if you feel this work should be reprioritized and explain why.

Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Maria van Keulen [ 29/Apr/20 ]

I think the find on system.profile was passing prior to SERVER-46900 because profile writes for transaction write operations occur in a side transaction. The find on system.profile would have been running in the same transaction as the insert operation that got profiled, so the find wouldn't have been able to see the writes to system.profile, since those writes occurred outside of the transaction's snapshot. Running the find on system.profile outside of a transaction does not have this visibility restriction.

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