[SERVER-36326] Check if sharding is enabled inside ~ScopedOperationCompletionShardingActions Created: 27/Jul/18  Updated: 29/Oct/23  Resolved: 30/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.0, 4.1.1
Fix Version/s: 4.1.1

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 50

 Description   

If the config database gets dropped while we are setting up config.system.sessions inside
LogicalSessionCacheImpl::_refresh, we will get a CannotImplicitlyCreateCollection error. This error is then handled inside the destructor of ScopedOperationCompletionShardingActions which tries to do getConfigServer(). This will trigger a segmentation fault if the cluster is not sharded. 



 Comments   
Comment by Githook User [ 30/Jul/18 ]

Author:

{'username': 'cheahuychou', 'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com'}

Message: SERVER-36326 Check if sharding is enabled inside ~ScopedOperationCompletionShardingActions
Branch: master
https://github.com/mongodb/mongo/commit/1325d6ae2d71456073adc89744dd712940227ef8

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