[SERVER-37372] Race condition in change_stream_update_lookup_read_concern.js Created: 28/Sep/18  Updated: 29/Oct/23  Resolved: 01/Oct/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.1.4

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2018-10-08
Participants:
Linked BF Score: 10

 Description   

As part of this test we have 3 nodes in a replica set, and we change the "tags" on two of them. See here.

After switching the tags, we wait for node 2 to acknowledge its new tag, here. We then run some node "targeting" tests, which assume that node 2 is the only node with the closestSecondary tag. However, node 1 may still have this tag, as we haven't waited for it to acknowledge its new tag, fartherSecondary.



 Comments   
Comment by Githook User [ 01/Oct/18 ]

Author:

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

Message: SERVER-37372 Fix race condition in change_stream_update_lookup_read_concern.js
Branch: master
https://github.com/mongodb/mongo/commit/175f5e3c25ddba439b7d28254a4af5504aded0d8

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