[SERVER-34481] Improve resiliency of awaitdata_getmore_cmd.js Created: 13/Apr/18  Updated: 29/Oct/23  Resolved: 17/Apr/18

Status: Closed
Project: Core Server
Component/s: Querying, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.6, 3.7.6

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Query 2018-04-23
Participants:
Linked BF Score: 15

 Description   

The test can fail if the currentOp which is looking for the getMore blocks waiting for a lock for longer than the getMore is running, as it looks like happened here:

[MongoDFixture:job0] 2018-03-22T13:11:28.047+0000 I COMMAND  [conn105] command admin.$cmd.aggregate appName: "MongoDB Shell" command: currentOp { currentOp: 1.0, op: "getmore", command.collection: "await_data", originatingCommand.comment: "uniquifier_comment", $db: "admin" } keysExamined:0 docsExamined:0 cursorExhausted:1 numYields:0 nreturned:0 reslen:35 locks:{} protocol:op_msg 4940ms



 Comments   
Comment by Githook User [ 03/Jul/18 ]

Author:

{'username': 'cswanson310', 'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com'}

Message: SERVER-34481 Increase robustness of awaitdata_getmore_cmd.js

(cherry picked from commit abc845fcf2178ed504629097b6ff11f89045e5b7)
Branch: v3.6
https://github.com/mongodb/mongo/commit/3b1d9e47493ca10fb99899cd5aa4a792249330c0

Comment by Githook User [ 17/Apr/18 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-34481 Increase robustness of awaitdata_getmore_cmd.js
Branch: master
https://github.com/mongodb/mongo/commit/abc845fcf2178ed504629097b6ff11f89045e5b7

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