[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: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| 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 |
| 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? |