[SERVER-30439] Fix dbCheck range checking Created: 31/Jul/17  Updated: 30/Oct/23  Resolved: 22/Aug/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.5.13

Type: Improvement Priority: Major - P3
Reporter: Ian Kuehne Assignee: Ian Kuehne
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-08-21, Storage 2017-09-11
Participants:

 Description   

We decided to change the meaning of the minKey and maxKey fields in the dbCheck invocation, so that the minimum is exclusive and the maximum inclusive instead of the other way around. Change that, both on the primary and in the oplog command.



 Comments   
Comment by Githook User [ 22/Aug/17 ]

Author:

{'username': 'ikuehne', 'email': 'ian.kuehne@mongodb.com', 'name': 'Ian Kuehne'}

Message: SERVER-30573 Add dbCheck command.

Also includes fixes for SERVER-30439, SERVER-30422 and SERVER-30618.
Branch: master
https://github.com/mongodb/mongo/commit/324bc4e858959bbd77d111bddb4b166048723312

Generated at Thu Feb 08 04:23:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.