Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.1
Affects Version/s: None
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2019-09-23, Execution Team 2019-10-07, Execution Team 2019-10-21

Background dbhash already exists in our JS testing. We should be able to add logic to that code.

A thought: might need to consider the performance impact of doing this and consider whether we should only turn background validation on a subset of tests so as not to slow down our testing too much?

depends on

SERVER-43711 ValidateAdaptor::validateIndexKeyCount should not compare in-memory and persisted checkpoint _id index entry counts

Closed

SERVER-43757 background validate must skip indexes whose persisted and in-memory idents do not match

Closed

SERVER-43777 Validate cmd with {background:true} should not yield cursors

Closed

SERVER-43828 WT compact calls must take the CheckpointLock so that it is mutually exclusive with validate cmd opening cursors

Closed

SERVER-43942 Track newly created indexes until they are part of a consistent WT checkpoint, and avoid background validating them

Closed

SERVER-42357 Periodically release locks during collection validation and check for interrupts

Closed

SERVER-43678 Background collection validation should take a MODE_IS collection lock instead of MODE_IX

Closed

is related to

SERVER-44125 Explore running the background validation test hook less frequently and/or changing the checkpoint frequency

Closed

(2 depends on, 1 is related to)

Assignee:: Dianna Hohensee (Inactive)

Reporter:: Dianna Hohensee (Inactive)

Participants:: Dianna Hohensee, Githook User

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Jul 23 2019 06:37:08 PM UTC

Updated:: Oct 29 2023 10:18:52 PM UTC

Resolved:: Oct 21 2019 06:39:01 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates