[SERVER-42641] Add does_not_support_causal_consistency tag to abort_transaction_thread_does_not_block_on_locks.js Created: 06/Aug/19  Updated: 06/Aug/19  Resolved: 06/Aug/19

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

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-08-12
Participants:
Linked BF Score: 9

 Description   

This test should not be run by the causally consistent passthrough suite.
It does write in the default session and then expects to read the document in a different session.
This suite automatically attaches "

{readPreference: secondary}

" to every read command so it's possible that the read goes to a minority secondary. And since it's from a different session, it won't wait until the node has the writes.



 Comments   
Comment by Xiangyu Yao (Inactive) [ 06/Aug/19 ]

max.hirschhorn, oh I just realized. Then this theory is wrong. Closing the ticket.

Comment by Max Hirschhorn [ 06/Aug/19 ]

Unlike the causally_consistent_jscore_passthrough.yml test suite, the causally_consistent_jscore_txns_passthrough.yml test suite doesn't change the read preference.

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