[SERVER-36115] invalidated_cursors.js FSM workload should ensure killOp is sent to same node as currentOp Created: 13/Jul/18  Updated: 29/Oct/23  Resolved: 09/Nov/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.0.5, 4.1.6

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Ian Boros
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
Operating System: ALL
Backport Requested:
v4.0
Participants:
Linked BF Score: 15

 Description   

When the invalidated_cursors.js workload is run in the concurrency_replication_causal_consistency suite, the $currentOp aggregation is sent to the pinned secondary, but the killOp command is sent to the primary. This can cause the test to fail due to an operation unexpectedly failing on the primary. We should ensure that the killOp command is sent to the same node as the $currentOp aggregation.

This probably also applies to the killCursors command in the same test, though that is less likely to collide across two nodes, since it is chosen randomly, unlike opIds, which are chosen incrementally.

This is the only FSM workload that is run in the causal consistency suites and uses killOp. We may experience a similar issue with killCursors in kill_multicollection_aggregation.js.



 Comments   
Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-36115 (part 2) add some tags to fsm tests

(cherry picked from commit 625e4e2007fe31b9253976eb3815bcfd354a1cf6)
Branch: v4.0
https://github.com/mongodb/mongo/commit/3ce263275fd3ddb072d3174d4d8c1b484adee65f

Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-36115 ban tests from causal consistency suites which use $currentOp

(cherry picked from commit 25b9611bded107a08a7dba7ec8abe670f6de42f1)
Branch: v4.0
https://github.com/mongodb/mongo/commit/ab37733b902fa84e1288983231aee0be55e4e40e

Comment by Githook User [ 09/Nov/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-36115 (part 2) add some tags to fsm tests
Branch: master
https://github.com/mongodb/mongo/commit/625e4e2007fe31b9253976eb3815bcfd354a1cf6

Comment by Ian Boros [ 09/Nov/18 ]

Not yet closing as fixed, as we've realized we have to add tags to other tests.

Comment by Githook User [ 09/Nov/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-36115 ban tests from causal consistency suites which use $currentOp
Branch: master
https://github.com/mongodb/mongo/commit/25b9611bded107a08a7dba7ec8abe670f6de42f1

Comment by Ian Whalen (Inactive) [ 01/Nov/18 ]

Assigning to Ian for BF Friday.

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