[SERVER-54623] Decrease number of jobs in causal consistency passthrough suites Created: 18/Feb/21  Updated: 29/Oct/23  Resolved: 21/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0, 4.4.11, 4.2.18, 5.0.4, 5.1.0-rc3

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Brett Nawrocki
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.1, v5.0, v4.4, v4.2
Sprint: Sharding 2021-10-18, Sharding 2021-11-01
Participants:
Linked BF Score: 34

 Description   

There have been a number of failures in various causal consistency suites where we're seeing commands time out during periods of 100% disk utilization on the RHEL 6.2 variant. We're currently running 3-4 jobs in each of the suites, and we should lower the number of jobs at least for this variant.



 Comments   
Comment by Githook User [ 23/Nov/21 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-54623 Wait longer for session collection in ShardedClusterFixture

Test suites using the ShardedClusterFixture could time out waiting for
replication after calling refreshLogicalSessionCacheNow during setup.
This was most commonly seen during periods of high disk utilization.
Instead of failing the test, wait however long it takes.

(cherry picked from commit 4dd7f84be70ee95893ecf863f2d82c79edb2b8df)
Branch: v4.2
https://github.com/mongodb/mongo/commit/417283d903c8234f7c444851a438275fa8a67e1b

Comment by Githook User [ 22/Nov/21 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-54623 Wait longer for session collection in ShardedClusterFixture

Test suites using the ShardedClusterFixture could time out waiting for
replication after calling refreshLogicalSessionCacheNow during setup.
This was most commonly seen during periods of high disk utilization.
Instead of failing the test, wait however long it takes.

(cherry picked from commit 4dd7f84be70ee95893ecf863f2d82c79edb2b8df)
Branch: v4.4
https://github.com/mongodb/mongo/commit/ee796bba0e00233950df5e4244b5c22a8711ccd4

Comment by Githook User [ 30/Oct/21 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-54623 Wait longer for session collection in ShardedClusterFixture
Branch: v5.0
https://github.com/mongodb/mongo/commit/6699c75fb23b5640c94a8c21fa4ad757a21f56b4

Comment by Githook User [ 30/Oct/21 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-54623 BACKPORT-10933 Wait longer for session collection in ShardedClusterFixture
Branch: v5.1
https://github.com/mongodb/mongo/commit/d9e3a5e961e3a837d778ae02ffde1281c1a7b87a

Comment by Githook User [ 21/Oct/21 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-54623 Wait longer for session collection in ShardedClusterFixture

Test suites using the ShardedClusterFixture could time out waiting for
replication after calling refreshLogicalSessionCacheNow during setup.
This was most commonly seen during periods of high disk utilization.
Instead of failing the test, wait however long it takes.
Branch: master
https://github.com/mongodb/mongo/commit/4dd7f84be70ee95893ecf863f2d82c79edb2b8df

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