[SERVER-34771] secondary_reads_timestamp_visibility.js should log the read concern level when asserting on counts Created: 01/May/18  Updated: 29/Oct/23  Resolved: 07/May/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Kyle Suarez Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-05-07
Participants:
Linked BF Score: 0

 Description   

In secondary_reads_timestamp_visibility.js we have loops like the following:

    for (let i in levels) {
        // We should see the previous state on the secondary with every readconcern.
        assert.eq(secondaryDB.getCollection(collName).find({x: 0}).readConcern(levels[i]).itcount(),
                  0);
        assert.eq(secondaryDB.getCollection(collName).find({x: 1}).readConcern(levels[i]).itcount(),
                  100);
    }

We should update the assertion message to mention the read concern level being used for that find; otherwise it makes it difficult to determine what's failing.



 Comments   
Comment by Githook User [ 07/May/18 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-34771 Log read concern level when checking document visibility
Branch: master
https://github.com/mongodb/mongo/commit/2b21ce68e3471d7540f567c3dfc308af16b8e704

Comment by Kyle Suarez [ 01/May/18 ]

Sent to the Storage Team backlog because this test was introduced as part of SERVER-34385.

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