[SERVER-36904] Fuzzer drops config.system.sessions and triggers invariant Created: 28/Aug/18  Updated: 18/Jun/19  Resolved: 18/Jun/19

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Misha Tyulenev
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File perf_workload_invariant.js    
Issue Links:
Depends
is depended on by SERVER-36104 LogicalSessions should destroy cache ... Closed
Duplicate
duplicates SERVER-39420 Remove in-memory boolean to indicate ... Closed
Related
related to SERVER-35222 Crash on the config server at expired... Closed
Sprint: Sharding 2018-10-22, Sharding 2018-11-19, Sharding 2018-12-03, Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-07-01
Participants:
Linked BF Score: 52

 Description   

The collection is normally sharded before being accessed. However, it is possible to drop the collection. This makes it unsharded, and the config server will attempt to create a ShardLocal instance when trying to access it since it will be targetting an unsharded 'config.system.sessions' collection.



 Comments   
Comment by Misha Tyulenev [ 18/Jun/19 ]

This issue is fixed in SERVER-39420

Comment by Janna Golden [ 02/Jan/19 ]

Sure, I just attached the perf workload I was seeing this in. I drop config.collections here which is likely a part of the root cause, and I think benchRun() may exacerbate the problem because it does not reproduce when I remove the call to benchRun().

Comment by Blake Oler [ 27/Dec/18 ]

janna.golden, you said in a meeting that you created a consistent repro of this failure? Could you upload that somewhere for further investigation of this issue?

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