Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1645-Milestone-3

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2020-08-24
Linked BF Score:
0
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

The ReplicaSetAwareService test is mistakenly ending up calling the VectorClockMongoD onStepUpComplete.

So far the test has always worked because such method call always resulted in a NOP, but that will not be the case anymore with the changes that are going to be introduced in ~~SERVER-49193~~.

is depended on by

SERVER-49193 Recover the VectorClock on shard primary step up

Closed

related to

SERVER-46201 Implement a generic ReplicaSetStateAwareService

Closed

Assignee:: Kevin Pulo
Reporter:: Pierlauro Sciarelli
Participants:: Andrew Morrow, Githook User, Kaloian Manassiev, Kevin Pulo, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 29 2020 05:56:08 PM UTC
Updated:: Oct 29 2023 10:05:00 PM UTC
Resolved:: Aug 12 2020 02:03:12 AM UTC
Confidence Status Last Update:: 11/Aug/20 3:24 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates