[SERVER-48300] Prevent spurious failure in kill_pinned_cursor.js caused by mongos background index check Created: 19/May/20  Updated: 29/Oct/23  Resolved: 29/May/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 4.5.1, 4.4.0-rc6
Fix Version/s: 4.4.0-rc8, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2
Participants:
Linked BF Score: 50

 Description   

The test assumes that there will only be one getMore running on the mongods at a time. This is not true because background jobs like the periodic sharded index consistency checker may run queries.

The test can fail because an assertion about the number of active getMores will trigger in rare scenarios.



 Comments   
Comment by Githook User [ 29/May/20 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}

Message: SERVER-48300 Prevent spurious failure in kill_pinned_cursor.js
Branch: v4.4
https://github.com/mongodb/mongo/commit/7e27b969b67b7edb9d96b241d751ba37f87ea43e

Comment by Githook User [ 26/May/20 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}

Message: Revert "SERVER-48300 Prevent spurious failure of kill_pinned_cursor.js"

This reverts commit 26effc710705d610dd16061c93612e02d0a2aa71.
Branch: v4.4
https://github.com/mongodb/mongo/commit/89f3a36faf61d2a0345f64d76cb1284b00397e69

Comment by Ian Boros [ 26/May/20 ]

This was merged to master:

https://github.com/mongodb/mongo/commit/fb5f0800379361d97c125e225416754c59b093c3

I'm reverting the 4.4 commit as it seems to have caused an issue, though I'm not sure why yet.

Comment by Githook User [ 21/May/20 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}

Message: SERVER-48300 Prevent spurious failure of kill_pinned_cursor.js
Branch: v4.4
https://github.com/mongodb/mongo/commit/26effc710705d610dd16061c93612e02d0a2aa71

Comment by Ian Boros [ 19/May/20 ]

It looks like this index consistency checker was only introduced in 4.4 so I doubt we'll need to backport this further unless we discover other similar background jobs that can run.

Generated at Thu Feb 08 05:16:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.