[DOCS-14187] Investigate changes in SERVER-54260: Ensure that DDL operations are only audited on Primaries Created: 04/Feb/21  Updated: 13/Nov/23  Resolved: 27/Jul/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.9.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: Jason Price
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-54260 Ensure that DDL operations are only a... Closed
Participants:
Days since reply: 3 years, 6 days ago
Epic Link: DOCSP-9747
Story Points: 3

 Description   

Description

Downstream Change Summary

This change will make all DDL operations be audited only on primaries, not secondaries.

Description of Linked Ticket

DDL operations are currently audited on primaries and secondaries. Unfortunately, the audit hooks for these operations are buried in the execution machinery which is invoked during parallel batch application. This means that synchronous file writes, to the log file, are performed in the critical path of oplog application, potentially impairing the node's ability to keep up with its primary.

We should prevent secondaries from emitting DDL audit events for replicated changes.

 

Note that we must still record DDL events for local, non-replicated changes. These are DDL operations on the local database, and any collection named system.profile.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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


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