[SERVER-84353] The test for stepDown deadlock with read ticket exhaustion is flaky Created: 20/Dec/23  Updated: 04/Jan/24  Resolved: 04/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.1, 7.3.0-rc0, 6.0.13, 5.0.24, 4.4.28, 7.0.6

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

Issue Links:
Backports
Depends
Related
is related to SERVER-75205 Deadlock between stepdown and restori... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2, v7.0, v6.0, v5.0, v4.4
Sprint: Execution Team 2023-12-25, Execution Team 2024-01-08
Participants:
Linked BF Score: 35

 Description   

jstests/noPassthrough/read_ticket_exhaustion_with_stepdown.js, added in https://github.com/10gen/mongo/pull/11511 for https://jira.mongodb.org/browse/SERVER-75205, is implicated in multiple BFs (linked). It should be made less flaky.

 

AC:

  • Some test of the deadlock behavior is ~deterministic (not flaky).


 Comments   
Comment by Githook User [ 04/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Don't use IIFE in read ticket exhaustion jstest. (#17836)

GitOrigin-RevId: bda2cbb376b7ef335835ee22b594d95b511da149
Branch: master
https://github.com/mongodb/mongo/commit/04d2e14980e930fcb3da294757d363bb39424f83

Comment by Githook User [ 02/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': 'brad.cater@mongodb.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (v7.2)
Branch: v7.2
https://github.com/mongodb/mongo/commit/99b38e174b363515fad2fadcec0280ee45419cca

Comment by Githook User [ 02/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (v7.0) (#17788)

GitOrigin-RevId: 54b7574d0f1e2f128e7eaacdc2edba5d4c0bff70
Branch: v7.0
https://github.com/mongodb/mongo/commit/351fd1575a443bfbc2217b40c0e4ab3f10524577

Comment by Githook User [ 02/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (v6.0) (#17785)

GitOrigin-RevId: 8be130040330600c77855c2573bb30a75a7b3cd7
Branch: v6.0
https://github.com/mongodb/mongo/commit/6c48703afebc36a2dbf7779f3ffa95152e852c60

Comment by Githook User [ 02/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (v5.0) (#17786)

GitOrigin-RevId: e352ed59414d0506458abdbe66887f22a4b5949c
Branch: v5.0
https://github.com/mongodb/mongo/commit/9a0c91dd9f58a8b8a0b700155a6efee3b7288e65

Comment by Githook User [ 02/Jan/24 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (v4.4) (#17787)

GitOrigin-RevId: c913540bd5d33dae52b9ed2bb3ac639c444702cc
Branch: v4.4
https://github.com/mongodb/mongo/commit/cc247d2c8318232274bef801d32cc9568d127967

Comment by Githook User [ 27/Dec/23 ]

Author:

{'name': 'Brad Cater', 'email': '152920274+brad-cater-mongodb@users.noreply.github.com', 'username': 'brad-cater-mongodb'}

Message: SERVER-84353 Make read ticket exhaustion with stepDown test less flaky (#17746)

GitOrigin-RevId: 231d6367ea3c7670a458ce00252d970979d7f5be
Branch: master
https://github.com/mongodb/mongo/commit/2ff8fff5b01eeda5722884c5fd104716117c9606

Comment by Brad Cater [ 21/Dec/23 ]

The flaky test was backported to multiple versions, so we must backport the fix, too.

Generated at Thu Feb 08 06:54:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.