[SERVER-26186] Use CountDownLatch in concurrency test workload create_index_background.js Created: 20/Sep/16  Updated: 04/Feb/22  Resolved: 04/Feb/22

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jordi Olivares Provencio
Resolution: Won't Do Votes: 0
Labels: stm, tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Sprint: Execution Team 2022-02-07
Participants:
Linked BF Score: 21

 Description   

The concurrency workload create_index_background.js creates a background index in thread 0, after CRUD operations have begun in the other workload threads. It should use the CountDownLatch semantic to coordinate this activity instead of relying on assert.soon on a collection query, where field "crud" exists.



 Comments   
Comment by Jordi Olivares Provencio [ 04/Feb/22 ]

We cannot share state between threads in the FSM workload suites as all state is thread local. Thus we cannot use a shared CountDownLatch instance between threads.

Closing ticket as it cannot be implemented.

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