-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
RSS Sydney
-
GregsList - 2024-09-03, PopcornChicken - 2024-09-17, MorningKaraoke 2024-10-01, BananaDuck - 2024-10-15, CookieFloss - 29/10/24, Party@Gregs - 2024-11-12, TeamTummy - 2024-11-26
Validation code is written in an ad-hoc and inconsistent way, this makes bus likely and maintenance difficult.
Take a high-level look at validation and consider ways to improve its design, with a goal of speeding up maintenance tasks.
- split to
-
SERVER-82278 validate command can report indexDetails valid:True even if indexes have not fully been checked
- Open
-
SERVER-83615 Treat maxValidateMemoryUsageMB as an absolute limit
- Closed
-
SERVER-89857 Investigate deduplicating reporting index inconsistencies in the error and indexDetails fields of validate() output
- Closed
-
SERVER-94826 Make multi-key-index repair off by default (and add a new option for it)
- Closed
-
SERVER-93556 Regularize collection/reporting of ValidationResults
- Closed
-
SERVER-96250 Move index-consistency's size limiters into validateResults
- Closed
-
SERVER-96691 Reduce memory consumption of 2nd-phase validate
- Closed