[SERVER-36763] refreshLogicalSessionCacheNow can error with DuplicateKey error in concurrency suite Created: 20/Aug/18  Updated: 20/Aug/18  Resolved: 20/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-14322 Retry on predicate unique index viola... Closed
Operating System: ALL
Participants:

 Description   

In testing a new fsm workload (multi_statement_transaction_kill_sessions_atomicity_isolation.js), running `refreshLogicalSessionCacheNow()` occasionally fails with a DuplicateKey error in the sessions collection. This behavior is unexpected as all of the writes to the session collection should be either upserts or deletes.


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