Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.0-rc0
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Storage NYC 2018-03-26, Storage NYC 2018-04-09, Storage NYC 2018-03-12, Storage NYC 2018-04-23, Storage NYC 2018-05-07, Storage NYC 2018-05-21
Linked BF Score:
58

Txns should do no waiting for locks, they should fail the lock acquisition immediately if there's any conflict. They should also abort the transaction if that happens.

depends on

SERVER-34829 Drop pending reaper must not delete the _dropPendingNamespaces entry until after the drop occurs

Closed

SERVER-34372 Drop collection command with majority write concern should wait until two-phase drop finishes

Closed

is depended on by

SERVER-34726 Deadlock with locally stashed transaction resources during profiling

Closed

SERVER-34800 The transaction aborter thread should acquire locks with a 0-second lock acquisition timeout

Closed

is documented by

DOCS-11716 Docs for SERVER-33244: Make all lock acquisitions for transactions have 0 second timeout

Closed

is related to

SERVER-34951 LockerImpl should invariant against active UninterruptibleLockGuard usage when _maxLockTimeout is set

Blocked

SERVER-34924 Treat LockTimeout as transient transaction error

Closed

SERVER-35023 Add server parameter maxTransactionLockRequestTimeoutMillis test

Closed

(3 is related to)

Assignee:: Dianna Hohensee (Inactive)

Reporter:: Spencer Brody (Inactive)

Participants:: Dianna Hohensee, Eric Milkie, Githook User, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: Feb 09 2018 09:00:45 PM UTC

Updated:: Oct 29 2023 10:34:52 PM UTC

Resolved:: May 14 2018 01:53:06 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates