[DOCS-13764] [Server] Forbid dropping config.transactions when there are prepared transactions (SERVER-48525) Created: 14/Jul/20  Updated: 13/Nov/23  Resolved: 11/Feb/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.2.9, 4.4.1, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Naomi Pentrel (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-48525 Forbid dropping config.transactions w... Closed
Participants:
Days since reply: 3 years, 30 weeks, 1 day ago
Epic Link: DOCSP-9747
Story Points: 2

 Description   

Description

Downstream Change Summary

If there is nothing in the docs that ever talks about dropping config.transactions, then probably no changes needed. But if there is, it needs to be qualified with this restriction.

Description of Linked Ticket

null

Scope of changes

Take a look through the docs and see what we mention about config.transactions. Possible this is a no-op for us.

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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