Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Minor - P4
Fix Version/s: 4.1.7
Affects Version/s: None
Component/s: Replication
Labels:
- ShardedTxn:Testing
- todo_in_code

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-12-03, Sharding 2018-12-17, Sharding 2018-12-31
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We should run a passthrough suite that supports starting transactions with various supported readConcern levels. One example would be the read_concern_majority_passthrough suite. A readConcern argument is only supported on the first command of a transaction, so we may need to make changes in set_read_and_write_concerns.js to make this work correctly.

depends on

SERVER-33739 Update set_read_and_write_concerns.js override for commands accepting "snapshot" readConcern

Closed

is related to

SERVER-38733 Change majority read concern transaction passthroughs to use local read concern

Closed

related to

SERVER-38569 Unblacklist remove_and_bulk_insert.js concurrency workload from sharded txn suites (currently times out on slow variants)

Closed

SERVER-43474 Complete TODO listed in SERVER-33983

Closed

Assignee:: Jack Mulrow
Reporter:: Will Schultz
Participants:: Githook User, Gregory McKeon, Jack Mulrow, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Mar 19 2018 06:58:24 PM UTC
Updated:: Oct 29 2023 10:33:35 PM UTC
Resolved:: Dec 21 2018 01:12:12 AM UTC
Confidence Status Last Update:: 12/Dec/18 6:34 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates