[SERVER-86340] Use a different feature flag to protect collections creation inside distributed transactions Created: 07/Feb/24  Updated: 07/Feb/24

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Sprint: CAR Team 2024-02-19
Participants:
Linked BF Score: 113

 Description   

SERVER-81498 added support for creating collections in distributed transactions and the idea was for some follow up ticket to handle the lack of prepare conflict support. That change was approved because the code is protected behind a feature flag that will never be enabled in production without the follow-up work being done.

However, there are some tests creating collections in distributed transactions getting executed with all the feature flags enabled. In order not to get failures in evergreen, we should consider protecting the code behind another feature flag that must be disabled both in production and testing enviroments.


Generated at Thu Feb 08 07:00:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.