-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
v3.4
-
Storage NYC 2018-08-27, Storage NYC 2018-09-10
-
23
If a big index key (>1KB) has been inserted in FCV 4.2 and then a downgrade happens, the big index key remains on disk. This makes the index validation fail in FCV 4.0 because FCV 4.0 does not allow big index keys. This behavior is expected as we wrote in the design of PM-284:
It is expected that a big index key inserted in FCV 4.2 causes the index validation in FCV 4.0 fail. The solution is to drop the index and run validate again.
Therefore, the fuzzer should keep in mind this assumption and not validate in this case.
- is related to
-
SERVER-43627 Remove v4.2 FCV handling from ValidationCollections JS test hook
- Closed
- related to
-
SERVER-37074 Validation hook should continue downgrading if a downgrade was interrupted
- Closed
-
SERVER-53359 jstestfuzz (mutational) fuzzer is forcing last-lts FCV during validate instead of latest
- Closed