[SERVER-30497] Investigate if itcount is not causally consistent? Created: 03/Aug/17  Updated: 30/Oct/23  Resolved: 22/Aug/17

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-08-21, Sharding 2017-09-11
Participants:

 Description   

Failure looks like find does not use after cluster time. Investigate if its related to itcount.



 Comments   
Comment by Ramon Fernandez Marina [ 24/Aug/17 ]

Author:

{'username': u'mikety', 'name': u'Misha Tyulenev', 'email': u'misha@mongodb.com'}

Message:SERVER-30497 update comments on the blacklisted tests
Branch:master
https://github.com/mongodb/mongo/commit/d268047046cfcaeeaccd118c1a81f1c7690dbbcc

Comment by Misha Tyulenev [ 22/Aug/17 ]

Thanks milkie this turned out ot be jsut a non deterministic test. This line

assert.eq(5, t.find({x: 2}).maxScan(50).itcount(), "D");

presumes ordered set.

Comment by Eric Milkie [ 03/Aug/17 ]

"itcount" is a shell helper that just exhausts a cursor by counting how many times it can call next(). So this probably involves "cursors in general", not just itcount.

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