Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.3.14
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2016-10-10
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

For parity with ReplicationCoordinatorImpl::waitUntilOpTimeForRead replication should also use the interruptible wait on condition variable for awaitWriteConcern.

This also brings us one step closer to not needing ReplicationCoordinatorImpl::interrupt.

is related to

SERVER-26190 Waiting for opTime or majority read concern is not interruptible

Closed

related to

SERVER-26305 Deadlock between replication stepdown and threads about to wait for read concern

Closed

Assignee:: Kaloian Manassiev
Reporter:: Kaloian Manassiev
Participants:: Kaloian Manassiev
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Sep 26 2016 11:40:49 PM UTC
Updated:: Sep 28 2016 03:06:03 PM UTC
Resolved:: Sep 28 2016 03:06:03 PM UTC
Confidence Status Last Update:: 28/Sep/16 3:05 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates