Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.20, 4.2.9
Affects Version/s: None
Component/s: Index Maintenance, Replication
Labels:
None

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

v4.4, v4.2
Sprint:
Repl 2020-07-27, Repl 2020-08-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

Normal replication recovery does, because shouldRelaxIndexConstraints returns "true" during STARTUP but shouldRelaxIndexConstraints returns "false" on a standalone, so recoverFromOplogAsStandalone does not.

is related to

SERVER-49529 setTableLogging error at startup while creating index entry, in backup/restore test

Closed

SERVER-49530 fix final index build phase for oplog recovery as a standalone mode

Closed

SERVER-49924 Forward-port SERVER-49527 to master branch

Closed

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Daniel Gottlieb, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jul 15 2020 03:58:16 PM UTC
Updated:: Oct 29 2023 10:05:47 PM UTC
Resolved:: Jul 27 2020 03:30:24 PM UTC
Confidence Status Last Update:: 15/Jul/20 4:12 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates