[SERVER-76231] Validate should not fail immediately when it detects out-of-order keys Created: 18/Apr/23  Updated: 29/Oct/23  Resolved: 14/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-76232 Do not crash when index inconsistenci... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-05-15, Execution Team 2023-06-12, Execution EMEA Team 2023-06-26
Participants:

 Description   

Instead of the command failing immediately when it detects out-of-order keys, we should report an inconsistency and finish scanning the data.



 Comments   
Comment by Githook User [ 14/Jun/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-76231 Relax validate early failure when detecting out-of-order entries
Branch: master
https://github.com/mongodb/mongo/commit/088159c703937444b0ee5f068b3203853aa88992

Comment by Louis Williams [ 15/May/23 ]

dianna.hohensee@mongodb.com yeah that is correct. The issue is that validate fails without completing. It's not reported as a validation error, but a command error.

Comment by Dianna Hohensee (Inactive) [ 12/May/23 ]

IIUC, we want the behavior to be that the error message is logged – and added to the validate errors response --, but the scan completes, ONLY for the validate command. Regular user reads will still log an error message and an uassert that ends the operation.

Is this correct, louis.williams@mongodb.com ?

Generated at Thu Feb 08 06:32:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.