Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Storage
Labels:
None

Sprint:
Execution Team 2019-06-17, Execution Team 2019-11-04, Execution Team 2019-11-18

In secondary mode, secondary batch application logic already handles visibility and holes in the oplog. Both the in-memory oplogReadTimestamp and the persisted oplogTruncateAfterPoint are updated. There's no need for the oplog visibility thread to run and use resources doing unnecessary work. (plus it would get confusing with batch application unsetting the oplogTruncateAfterPoint while the oplog visibility thread keeps setting it)

depends on

SERVER-41391 Clear the oplogTruncateAfterPoint timestamp on stepdown

Closed

SERVER-44180 replicationBatchIsComplete() should prompt the WiredTigerJournalFlusher thread to run instead of the _oplogJournalThreadLoop

Closed

is depended on by

SERVER-41392 Modify the _oplogJournalThreadLoop() to no longer call waitUntilDurable() and instead update the oplogTruncateAfterPoint

Closed

Assignee:: Dianna Hohensee (Inactive)

Reporter:: Dianna Hohensee (Inactive)

Participants:: Dianna Hohensee

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: May 30 2019 01:28:15 PM UTC

Updated:: Nov 18 2019 01:23:58 PM UTC

Resolved:: Nov 18 2019 01:23:58 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates