Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Critical - P2
Fix Version/s: 3.2.13, 3.4.4, 3.5.5
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.4, v3.2
Sprint:
Repl 2017-01-23, Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27
Case:
Linked BF Score:
19
Confidence Status:
None
Work Order:
0

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

When the document returned by the GTE query against our sync source does not include our most recent optime (ie the term and timestamp of our most recent oplog entry), we currently unconditionally return OplogStartMissing and go into ROLLBACK. The GTE query only includes the timestamp however, not the term, so we need to check the term and if the optime (including term) of our most recent oplog entry is higher than the optime we got back from the GTE query, we should not go into rollback but should just choose a new sync source.

depends on

SERVER-27050 Ensure upstream node doesn't roll back after checking minvald

Closed

SERVER-27543 Create new metadata for oplog queries

Closed

is duplicated by

SERVER-19753 Do not allow force sync from stale source

Closed

SERVER-26253 Get new sync source rather than rollback on RemoteOplogStale error

Closed

SERVER-27672 Unnecessary rollback for a hidden node after a priority takeover reconfig

Closed

SERVER-27980 Secondary tries to rollback when it lagged to much behind primary

Closed

is related to

SERVER-27547 Adjust the system time . then MongoDB status maintian RECOVERING

Closed

SERVER-28068 Do not go into rollback due to falling off the back of your sync source's oplog

Closed

SERVER-28278 Wait for desired sync source to replicate dummy write before running replSetSyncFrom in syncFrom shell helper

Closed

SERVER-27545 Include RBID in replSet metadata of command replies

Closed

related to

SERVER-27149 Sync source selection doesn't consider terms

Closed

SERVER-26253 Get new sync source rather than rollback on RemoteOplogStale error

Closed

SERVER-28377 Do not check that remote last applied is ahead of local last fetched in OplogFetcher first batch during initial sync

Closed

SERVER-28686 rollback_after_sync_source_selection.js should wait for rollback to complete before stopping replica set

Closed

SERVER-28430 Expose dropConnections() method on ConnectionPool through the NetworkInterface

Closed

(1 is duplicated by, 4 is related to, 5 related to)

Assignee:: Judah Schvimer

Reporter:: Spencer Brody (Inactive)

Participants:: Eric Milkie, Githook User, Judah Schvimer, Kelsey Schubert, Mathias Stearn, Siyuan Zhou, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 15 Start watching this issue

Created:: Dec 13 2016 04:24:47 PM UTC

Updated:: Aug 29 2018 08:53:42 AM UTC

Resolved:: Mar 08 2017 10:18:15 PM UTC

Confidence Status Last Update:: 10/Jan/17 8:01 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates