[SERVER-40899] Disallow chaining in change_stream_update_lookup_read_concern.js Created: 29/Apr/19  Updated: 29/Oct/23  Resolved: 08/May/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.11, 4.0.12

Type: Bug Priority: Major - P3
Reporter: Justin Seyster Assignee: Justin Seyster
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: 25

 Description   

The change_stream_update_lookup_read_concern.js test creates a repl set and assumes that the two secondaries both sync from the primary. In a few cases, the TopologyCoordinator instead syncs one of the secondaries from the other. The test is supposed to temporarily turn off replication on one secondary, but the unfortunate chaining situation means that replication effectively gets disabled on both secondaries, deadlocking the test.

Disabling chaining should prevent this failure from occurring again.



 Comments   
Comment by Githook User [ 26/Jul/19 ]

Author:

{'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}

Message: SERVER-40899 Nix chaining in change_stream_update_lookup_read_concern

(cherry picked from commit a420f5c73bef41aa804a390997897c059afa3713)
Branch: v4.0
https://github.com/mongodb/mongo/commit/1163d6594381a07cd95a16142166d0c326447360

Comment by Githook User [ 08/May/19 ]

Author:

{'name': 'Justin Seyster', 'username': 'jseyster', 'email': 'justin.seyster@mongodb.com'}

Message: SERVER-40899 Nix chaining in change_stream_update_lookup_read_concern
Branch: master
https://github.com/mongodb/mongo/commit/a420f5c73bef41aa804a390997897c059afa3713

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