[SERVER-40589] find command should validate $_internalReadAtClusterTime is not null Created: 11/Apr/19  Updated: 29/Oct/23  Resolved: 22/Apr/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.1.11

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

Issue Links:
Depends
Related
is related to SERVER-39169 Add testing-only support for doing sn... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

(function() {
    // resmoke --suite=jstestfuzz_replication repro.js
 
    assert.commandWorked(db.coll.insert({a: 1}));
 
    // Invariant failure !(provided && provided->isNull())
    assert.commandWorked(
        db.coll.runCommand('find', {$_internalReadAtClusterTime: Timestamp(0, 0)}));
})();

Sprint: STM 2019-05-06
Participants:
Linked BF Score: 7
Story Points: 1

 Description   

The 'find' command will hit an invariant failure here when a command sends a null timestamp, Timestamp(0,0).



 Comments   
Comment by Githook User [ 22/Apr/19 ]

Author:

{'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}

Message: SERVER-40589 Disallow $_internalReadAtClusterTime with null timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/cda363f65bde8d93a7c679757efd3edf7c6e8ad9

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